According to Lars Schneider's comment, "git lfs clone" is obsolete now. http://smartgit.userecho.com/topics/65-gui-for-git-lfs/

Please have a look at: http://www.syntevo.com/doc/display/SG/System+Properties#SystemProperties-smartgit.log.graph.layoutActions

Please give more details on performance problems: do you have a comparison for the same repository with and without junctions?

Thanks, description is updated.

Please make a suggestion for the description change.

I think we should make the description of this topic clearer, so one can understand that (1) syntax highlighting can already be switched, but (2) what are the shortcomings of the current approach and (3) which faster solution is suggested.

Right; after a successful fetch, failed entries could be removed as well. But now this overall won't be easier than grouping.

> What if there were failed background fetches (some connection problems) and then successful fetches?

> You'll always see one successful fetch after a bunch of not successful?

Easiest way would probably be to hide all successful Fetch entries, so you would only see failed entries. 

Thanks :)

I think the suggested grouping would only be useful for background fetches. What would you think of instead auto-removing successful fetch entries?