While refactoring some code, I often have to split up large files into smaller ones. This results in loosing the history of all code which is relocated from the original file.

As a countermeasure I found this workaround for git:

- first duplicate the original file (copy it using a new filename and/or location)

- commit this duplication without any changes (this is a commit which might not build properly)

- remove the duplicate code from both files

- commit changes (this commit should work fine)

On the commandline, using "git log --follow" it is now possible to track all changes of the new file across the duplication step. With smartgit this does not work; smartgit seems to follow renamed files only.

I would like to propose a (maybe optional) follow-copy-strategy in the log view - from my point of view only exact copies need to be detected, which should keep the cost at minimum.

E.g. if any branch heads to any commit included in the branch currently checked out, show it's label instead of showing just the branch currently checked out local and remote labels.

It is extremely common that one starts a feature or bug prior to actually starting the GitFlow process. This means there are often unstaged changes before starting a GitFlow bug/feature. When you do this, it will fail as there are uncommitted changes when it needs to change branch/make a branch/etc.

Unfortunately SmartGit isn't automatically stashing/unstashing in response to this. Which makes using GitFlwo very frustrating.

It should be no issue to stash all changes, perform the GitFlow process, then unstash.

I use Gerrit with Smartgit for many repos but Gerrit was never detected by Smartgit despite claimed support.

Documentation says:

SmartGit will detect a remote as being connected to Gerrit, if:

• .git/hooks/commit-msg exists; and
• there is only one remote overall or it's the only remote connecting to port 29418 (default Gerrit SSH port)

The second condition is clearly too restrictive. Repos I work with use port 29420 so I'm doomed to never see them detected with current detection method.

For now the GitFlow button can't be added in the log window toolbar... I miss it lots of time when preparing / finishing a release !

Add the ability to expand or collapse everything in the Branches Tab. This will recursively go through every branch and tag, and expand (or collapse) those that are grouped together.

It seems to me that the submodule options found in the Remote > Submodule menu should also be available when right-clicking on the root of a specific submodule.

Reduced branch graph, more compact/less information as the current Log. See the images for example here:
https://git-scm.com/book/de/v1/Git-Branching-Einfaches-Branching-und-Merging

If you set a keyboard shortcut for, say, "Next Change", in the "Index Editor" window will not work. The "Customize..." menu also points to this behavior by printing "Changes | Next Change" instead of simply "Next Change"