Your comments

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 !

Thomas, I didn't understand your last answer, can you explain more ?


For now the option is present when pulling, but is pretty well hidden. Indeed we did install some new SmartGit instances recently and despite our well written procedure we forgot twice to change the option, which caused our logs to become mad again.

And if you don't change it on the first pull then you'll have to re open each branch on which you already pulled with the wrong option right ?


The different solution I see :


* Changing the default option value

Reading your first comment I understood you don't want to change this ? But I can say SmartGit is the only Git client I have used that have this behavior by default, and that it is VERY annoying.


* Add a screen in the install wizard that let you choose the default option value


* Have a way to change the default behavior globally, including already pulled branches

I've just saw a strange behavior. I saw the green arrow, but nothing was fetched. I add 300 value for both delay options... I quit, changed to 1 for fetch, and then restart : nothing changed after all the favs repo were updated. I waited 5 min, the fetch was finally done. I'm wondering if SmartGit does a fetch only if the last poll gives an update ? So you'll have to wait 2 poll delay before the first fetch occurs ?