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

Thanks, I'll try this !

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 ?

Done : http://smartgit.userecho.com/topics/223-/

Thanks !

After a few hours using SmartGit with custom poll/fetch options, seems perfect to me. Many thanks !!

But it should be more visible for the user : add those options in the preferences, or at least a link to the documentation ?

Yes, there should be at least a way to change it globally. After you've installed SmartGit (might be an option in the installer right ?) And for an existing installation also... Because for now if you forget to change the option immediately after cloning or opening for each repo, then you are in trouble :(

Thanks :) Can you also add in the doc the default values ? Is the poll mandatory ? I'm only interested in the fetch...

All the background options were checked indeed.

Thanks very much for the documentation page, very interesting !! I've just tried, but seems poll.delay and fetch.delay are to be expressed in seconds, not minutes as stated in the page right ? (I began with a 5 value and SmartGit didn't stop updating repo...)

Certainly Colin, that was why I was talking about the impossibility to customize this behavior in SmartGit :o)

Please note though that in my company we are using an on premise instance of GitLab (and previously Gitolite). Both worked great with SourceTree.

With SmartGit, I can't understand how often it fetches the repo, but it's almost never at the right time for me... It's strange also because I see sometimes the down green arrow, but the journal view has almost never the updated content, neither the log window.

I don't pull so often : maybe once or twice a day on the 15 or so repo I'm working on. So waiting for this to be fixed, I'm primary using the GitLab activity page.

Thomas, this is not a satisfying answer : you can't control how often the repo are fetched first of all. Using SmartGit everyday I almost everytime needs to do my fetch/pull manually. SourceTree is great for that, the remote changes appears almost immediately and for each commits to pull you can see every changes made.