Please note that some commit messages in some repositories are indeed whole documents. Having a tooltip cover the whole screen seems not useful for me.

Just start typing the repository name.

The fonts and sizes are defined by the operating system.

The 18.1 preview will start soon.

Have you tried to select both commits in the log - the last commit and the remote commit?

Currently, you have 2 Options:

- create a tiny script that invokes git diff > patch and add this as external tool (https://stackoverflow.com/questions/5159185/create-a-git-patch-from-the-changes-in-the-current-working-directory#15438863)

- stash the changes and create the patch from the stash commits

Will be fixed in 18.1 preview 1.

What if the commit 1 is the one with a preparation change and commit 2 being the final feature's change with the appropriate message (a common situation for us)? Do you really suggest 2 different operations that differ just in the way messages are handled?

You already can squash commits easily in the Journal.

90% of the SmartGit updates will be downloaded in the background, e.g. from 17.1.0 to 17.1.1. They will be applied unnoticable by restarting SmartGit. Only if some files outside the *.jar files have to be replaced, e.g. when updating from 17.0.* to 17.1.*, a longer "genuine" update is performed. This "genuine" update process only takes a long time on Windows and is built to be as robust as possible, e.g. instead of directly messing with the existing installation, it creates a second one parallel to the current one and later simply renames the directories and removes the old directory structure. This takes longer, but has the advantage of keeping a working directory structure as long as possible.