I need to try installing SmartGit from scratch... Will do and i'll get back to you.

Not sure to understand your answer Thomas ? Reading Marc I understand that in both windows there are indeed lots of views that are similar but with different functionalities, and that merging everything would be a great amount of work. But from my experience, stating this is usually a clear sign of a bad design...

Do not get me wrong, I use SmartGit everyday, but indeed this two windows interface is really annoying, and gives a very bad feeling to first starters : in a versionning product, the log/history should be the center piece, you shouldn't have to open a new window to use it !

With my previous comment I was just adding my 2 cents, saying that for SourceTree Atlassian chose an interface that is much more clearer and usable, and still it provides in one window certainly all of the functionalities SmartGit gives in two windows(? to be confirmed - but at least there is all that I need).

Getting back to the feeling : by default you see all of the previous changes, all of your current changes (commited / staged / unstaged), and all of the remote changes. The minimum anyone would asked to a versioning tool.

As a downside in SourceTree you can't do blame / history of a single file. Not sure this is so much of an important functionality though : for this usage any developper has his IDE that is much more practical ! This is typically a functionality that I wouldn't mind if it opens up a new window.

It might not be easy, but maybe there's an interface to totally rethink, looking at what other products do. I really think this is the worse default of SmartGit right now, and believe me it's hard to find others ;)

Sorry I still don't understand. The dialog opening depends on the pull.rebase option in ~/.gitconfig. As we didn't see the dialog in newly fresh installs, my questions :

• is the dialog only present in recent builds, ie not present in 8 and downwards ?
• is the pull.rebase option added by anything other than SmartGit ? Can it be already fixed when launching SmartGit for the first time ?

Eclipse IDE has 2 background colors, one for space between views and one for view content, the later being darker than the first one. This seems like a good solution for icons text and tab labels ?

Yeah ok, after some hours using this "dark" SmartGit, there are indeed some progress to do.

Besides the 2 problems I've already list :

- in treeviews (repositories, branches, output, ...) the icons are almost black, so almost invisible
- the compare marks colors on right ruler are not bright enough so it is difficult to clearly see them
- no color for highlited lines on non selected views : for exemple, in the log, click on a commit, then on a file : you can't see anymore which commit is selected
- color for repo with modifications is too dark

Thanks ! It's definitively a big change !

I need to use it more to have an opinion, but on a first look I can see 2 problems : icons text in the toolbar are black, so you almost can't read them. Also, the view names have a grey background, it's a bit to bright.

But anyway it's a very very good start, bravo !

Ha sorry, didn't understood there was only the checkbox problem ! Thanks for the capture, it looks very fine by me, I would love to be able to use it !!

Pretty naive comment but as Eclipse IDE has a dark theme, they may have use some workarounds that can be used also for SmartGit ?

Ok, your proposal is that on each repo when you pull for the first time you would get this new dialog ? This gives more visibility to the option indeed... could a good solution as a first step.

But I'm still concerned that new developers would miss the step even having this option exposed as clearly... And by the time someone else on the team notice, he'll have dozens of repo configured with the merge commit option instead of rebase. In this case, you'll have to change every branch manually, which is quite a pain :/

Hi, since yesterday the values poll 300 and fetch 120 gives pretty good results for me. I've also activate the DEBUG but not sure to understand the log content : polling seems to occurs multiple times per minute ? I'll send you this by mail as proposed.

Many thanks !