Unfortunately the dumps did not cover the problem: you have to invoke Create Periodical Thread Dumps before opening/closing the repository. Btw, how many (tracked) files does the repository contain? Can you also provide a clone URL, so I can see how long it takes for me?

Could it be due to a cold file system cache? If closing and reopening the repository again, does it become faster? Please also generate periodical thread dumps during closing and reopening a few time:

http://www.syntevo.com/doc/display/SG/Periodical+Thread+Dumps

Please give 17.1 RC a try and let me known whether this works better for you.

I was successfully using the mentioned property with my SVN Kerberos test system. For Git, things may be different.

Investigate (DeepGit) already honors the selected line from the Changes view.

SmartGit currently is not using the GitHub "release" API at all. So your suggestion is to combine the API with SmartGit's Git-Flow? Are you aware of some "reference" Git-Flow implementation which is using the "release" API already?

Closing as duplicate. Please vote for issue #224.

This seems to be a duplicate of http://smartgit.userecho.com/topics/224?