When rewriting history via the journal (i.e. interactive rebase) runs into a conflict, it currently completely aborts (seems like "rebase --abort"). Like in native rebase --interactive I would like the opportunity to choose between 1) resolve the conflict and continue and 2) abort the interactive rebase.

If you check "annotated tag", you must fill out the Message field in order to press Ok.

If you do not check "annotated tag", then the Message field is grayed out.

So the checkbox is redundant with the message box. If you fill in a message, it should automatically become an annotated tag, and if you don't, then it shouldn't.

Large repositories, such as Qt's git://code.qt.io/qt/qt5.git contain multiple submodules. The normal workflow doesn't necessarily include all of those submodules. Allow the user to selectively enable only the submodules she desires.

By default the application when rewriting the history uses git push --force (in the case of GIT).

It woulf be good that it rather (or at lease give the choice) uses --force-with-lease which is more secure.

Currently, Branches with the same name before a forward slash are grouped together, but Tags are not.

Source Tree does the grouping for both Branches and Tags, plus they have a nice folder icon for it for a more pleasant UI experience.

Quickly see what the stash would change of applied to the working copy, summary of change files woudl be good, this woudl allow you to dop an irrelavant stash quickly and easily

Right now I can't see any branch from remote SVN server if the branch name contains '/'. For example 'feature/15232_pathfinding' is displayed as 'feature' and I'm unable to check it out. Furthermore I cannot create a brach with '/' in it. Tortoise SVN allows to operate with such names so it would be great if SmartGit would also understand them.

Currently, when working with groups of repositories whenever one repository is being updated/pulled/pushed, UI (logging etc) is disabled for all other repositories.

Would it be possible to update SmartGit to the latest version of Git for Windows?

Being able to use color schemes in mintty is a feature I'm really looking forward to use.

For example, every time I am pushing changes to Gerrit I have to:

1) Remote -> Push To

2) Select Target Repository to be Gerrit (I have multiple origins and Gerrit is not the first one)

3) Check "Custom Ref"

4) Push

I would love to have all those steps under one button on the main bar. It gets kind of annoying when you push often.

Another thing is squashing commits to one. Gerrit requires a CL to be single commit. Squashing is a lot of clicks.