Currently when a signing key expires, smartgit only shows the attached message.
The log file also only outputs that gpg2 failed to sign a commit.

I'm not sure if you actually get more output by git/gpg if it fails to sign a commit with an expired key. If so showing that info or logging it at least would be nice.
In either way it would also be nice if smartgit does warn that this might be the reason, or could just make a quick check in the settings dialog if the specified key is still valid.

I know that it's a little bit of extra feature, but this really threw me off when it just stopped working after some years and the "user experience" is really bad. I just happened to invoke gpg2 -k and finding that the entry for my key is actually expired. Just re-running the smartgit command displayed below to debug it by yourself is obviously not possible as the tmp file is gone.

Description: Add one or two columns in the Files view, indicating how many lines were added/removed

Scenario: I want for a commit, or for a diff between 2 commits, find which files contain most changes in order to quickly assess the risk of this merging this change to a release. Therefore I would like a column to indicate this, so I can sort on that one.

Example from TortoiseGit UI:

Making it easy to add the git, bash, ssh and other utilities to the PATH of the Windows machine where SmartGit is installed

We have users that also install “Git for Windows” and then use that for command line git – which can lead to different version of git with different setups leading to problems.

If the SmartGit installer could just register its directories on the PATH then people would only have to install one tool.

Add ability for user to set the default GitFlow configuration with an option to automatically initialize GitFlow per the default upon any cloned repo or upon any cloned repo for an enterprise. 

Users coming from Atlassian SourceTree are used to Mixed being the default. And, I almost never use hard reset, though others clearly do.

If you rebase interactively, and need to edit the message of multiple commits, you have to use the mouse to double click the entries, because pressing enter starts the rebase, even though cmd + enter starts the rebase too.

Instead, you could use enter (edit commit message) > reword > enter (to confirm the message) > down arrow > enter (edit commit message) > etc., which would be a lot faster.

When you use the next change button with multiple files in the working tree (or in a commit), a temporary tooltip with the file name shows up right in the middle of the changes, so it obscures some of them.

It would be nice if you would be able to completely disable them, since the file name is already displayed in 2 different areas of the current window.

The last typed word is never spell checked, not even after a pause. This means that a typo in the last word of a commit message is never underlined, so, easily missed.

Currently I can see the git tags in the branches window on the same level as "Local Branches" or any remote.

I have the situation, where I have the exactly same tag name on different remotes. The remotes contain related history and are all added to one local git repository.

It looks like Smartgit only shows the tags for 1 of the remotes and I can't figure out, (within SmartGit) which remote contains which tags.

It would be great, if Smartgit could display all tags from all remotes.

One solution would be to show the tags within the corresponding remote or to show the tags in a similar style like it is done for remote branches with the same name (Remote1/Tag1, Remote2/Tag2 etc.).

Support for negative refspecs would be great. It seems SmartGit does not understand it's syntax yet because I get an "Command Failed - Invalid wildcards ^refs/heads/something-to-exclude/*" error when using them.

See Stack Overflow and implementation.