SmartGit continues to improve at a good pace and the Preview releases are a great way to try the improvements.  I've become so used to regular Preview releases that I'm almost sad when a new build isn't available to try!  ;-)

For 18.1 Preview, the "Reworked Compare" feature is my personal fav as I'm diffing all the time and this change helps automatically narrow to what's truly changed vs me manually hunting in a highlighted block for what changed (slow and painful!).

Thanks guys!

Clicking the Pull button pops up a dialog window of the options, which I almost never use, and requires user to press Enter or click.  If I need to do pull options, the button's drop down menu has them.

This is also true of the context menu's Pull... and Ctrl-P shortcut, but those work as is.

Clicking the Push button immediately does the push.  If I need to adjust the push, the button's drop down menu has it.

To aid in diagnosing merge issues and checking when events occurred add the date and time stamp to each node in the output tab

The rows can be reverted only in standard changes view, not in compact one. I don't know, if it is because of any technical 

if your submodules fail to check out - you have 2 reset each one by hand instead of resetting them all at once

I would really like the ability to stash hunks from my working directory into a named stash by selecting such hunks from in a "Index Editor"-like window.

This would basically be a user friendly interface to the awesome git stash --patch command, and would allow avoiding to do git add -p & git stash -k. The ideia is obviously taken from Mercurial shelves extension (and the support to do "graphical" stashing provided by some other tools).

Shallow repos are extremely useful when working with huge repositories with long histories and large amounts of data (like binaries).

Since git 1.9 (with better support since 2.5), git has fully supported shallow repos (you can push/pull to/from the remote, etc), and is now very configurable. This lets developers pull down only a small amount of the history, making it faster to work locally (due to less data in the repo that needs to be maintained), and also avoiding the need to pull huge amounts of data over the network when cloning.

SmartGit currently has an option, when cloning a repo, to clone only to a specific depth. However, this is not sufficient for fully supporting a 'shallow repo' workflow, for the following reasons:

Missing functionality:

• If you wish to clone to a specific depth, you only have the option of doing so if you un-check the "fetch all heads and tags". There is no support for fetching all heads so long as they are within the desired commit depth (the "--no-single-branch" option in 'git clone').
• No support for choosing --shallow-submodules vs --no-shallow-submodules when cloning.
• There's only an option to clone to a depth, and not "clone since date" (the "--shallow-since=<date>" option in git clone/fetch)
• No support for --shallow-exclude in clone/fetch/pull
• No way to change the desired depth after cloning (that I could find), to use subsequent fetches/pulls to trim or fill-in the history
• No support for --unshallow, --update-shallow, or --deepen-shallow when fetching

Bugs (as of SmartGit 17.1 preview 6 #11041):

• Regardless of what depth you clone to, when SmartGit does a subsequent fetch, it does not specific the desired depth, so you end up pulling the entire repo anyhow. This defeats the purpose of a shallow clone

This request is similar to https://smartgit.userecho.com/topics/395-implement-a-light-version-of-repository-management/ but expands upon it significantly.

gitflow's last update was about 4 and a half years ago. It's no longer maintained so no new features and more importantly no bug fixes. gitflow-avh is the most popular fork of gitflow and remains active to this day. According to the author of gitflow-avh both Debian and Ubuntu have switched to his fork to provide the git-flow package which is a very good indicator that the original project has died and that AVH is a suitable alternative.

Investigating history of commits with many merges can be a real pain. One useful feature is to be able to locate merge base. Not only for merge commits (though it would be useful on its own), but also for arbitrary pair of commits.

On browsers (well, atleast in chrome), if you have a really wide webpage (Trello for example) You can use Shift+Scroll to scroll wideways rather than up and down.

It would be nice if I could do this on Compare Panel too. For comparing long lines of code.

Not normally a problem, but I have a monitor in portrait orientation, and if you are using Index Editor, it doesn't leave much room. I just noticed it was missing was all.