It would be nice if there were filtering options for the repository pane like:

• Show repos with incoming changes (green down arrow)
• Show repos with outgoing changes (red up arrow)
• Show repos not on the default branch (i.e. master)

Currently, this is only available by the command line with the commands: 

1. git diff 
   
2. git diff --cached

The first thing I thought about to do to create a format patch for a range of commit was to select all commits like this:

But only after a long time I figured out how to create a format patch for a range:

1. https://github.com/deathaxe/sublime-a-file-icon-old/issues/1#issuecomment-447904728
2. https://github.com/gitextensions/gitextensions/issues/5923
3. https://smartgit.userecho.com/communities/1/topics/423-functionality-to-create-a-range-of-patches-all-labelled-sequentially

Only after luckily accessing these links in sequence, I figured out SmartGit already supported the format patch feature for several commits (I was just not selecting things right https://smartgit.userecho.com/communities/1/topics/890-hard-to-understand-the-format-patch-range), because every time I did the selection a range of commits (as in the picture), the SmartGit format patch option disappeared.

I am not sure why I need to double click on it, because when I am selecting it (single click) on something, I already would like for it to open.

If the log view is restricted to a directory or file and only commits affecting this subtree are shown all review features are disabled. This makes sense for most of them like creating pull requests but it would be nice to be able to add review comments to commits and files even if the log view is filtered.

If I want for exmaple to review the changes of a specific Java package I would show the log for this folder. If I now want to make a comment I have to remeber the ID of the commit and look it up in the unrestricted log view. If I want to make a line comment I now have to select the file and scroll to the affected line and then add the comment there. A similiar case would be git blame where the log is automatically restricted to the file if I show the changes. The workflow would be more fluent if I could directly add the comment.

The auto stash feature is great when switching branches and a conflict occurs.

Regularly, I find that I want to apply the one or more stashed files with conflicts anyway, overwriting the workspace files.

I have not found an easy way of doing that; does one exist? 

If not, can we have an "Overwrite" option to Apply Stash?  This would work best with 642-cherry-pickrevert-allow-to-select-the-files-to-cherry-pickrevert on a per-stashed-file basis to limit to one file too.

When using the Working Tree window as primary environment, showing the current working tree state in the log again when using the "Log" button for a repo is not very helpful for two reasons:

1) This information is most likely the same that was present in the Working Tree window that opened the log

2) Selecting the last commit requires an extra step

3) SmartGit needs to assemble the list of changed / new files, although this information is most likely never needed coming from the working tree.

Therefore, it would be good to have an option to switch directly to the last commit. The working tree state still can be at the top of the list, but it should be possible that this is not the entry with default focus.

To be able to easily scan for significant commits or files, please:

1. Add to Log window columns for (Added Lines) and (Lines) similar to "git log --shortstat"; A graphical column as in "git log --stat" would also be welcome.
   
2. Same in Commit view for each file similar to "git log --stat" and "git log --numstat"

      3. Size of changes in KB would be great for scanning for large binaries, but I cannot provide a command line equivalent.

Currently they feel like 2 pixels wide and it can take some slow careful mouse movements to hit the right location (at least on windows).

Now, when an error occurs during pushing a pull request, the message is lost, and I have to retype it. This can happen easily, for example due to hooks.