It is not our intention to simply copy the command line features in SmartGit, but rather find solutions that better suite a GUI application, especially for those users who have not used the command line Git.

Is it necessary for you to have it in the interactive rebase or would it be sufficient to select the commits and then choose Modify or Split Commits from the context menu?

I'm not convinced whether it is the best thing to pollute each command that somehow commits with such a low-level option. Maybe we should add it to the repository settings?

In the SmartGit settings directory is a gravatar-cache directory. There you can store "<email-address> <size>.jpg" files (size=32, 64, 128).

Please note, that Pull might be a destructive operation - it can product conflicts, especially if there are local changes. I would prefer to avoid getting reports about: "SmartGit screwed up my files when I clicked into the SmartGit window."

Note, that the toolbar commands perform exactly the same as the corresponding main menu item.

Please send a tiny test repository and exact steps to reproduce to smartgit@syntevo.com. Thanks in advance.

Thanks. Could you please illustrate by an example? What files? When exactly should SmartGit offer what message formatting/radio button? Please try to explain as detailed as possible to someone who does not know "convential changelog", because this increases the likelyhood of an implementation.

If "Automatically set up tracking for new branches" is selected and you push the new local branch, it will track it automatically. I reckon this makes sense in 99.5% of new pushed branches.