Your comments
(Don't know what you mean with "in the review)
For 17.1 the Changes-view in compact mode will remain read-only. The staging/unstaging requires large changes.
My problem with this keymapping is that you will need to use 2 hands. Using a one-key-combination for the most often used command (go to next change), seems to be better for me - at least for the file compare.
In the Log's Files view please select the toolbar button "View all files of the selected commit.".
For splitting commits there is a different command and the latest build 11129 (Help | Check for Latest Build) implements the split using duplicate commits (according to your suggestion), stopping at the first to discard unwanted parts.
What kind of icon do you suggest?
Sorry, I misunderstood you. The incorrectly named "diverged"-warning will be changed to a "behind checkout target" message.
I've changed the request's title so I better understand what I think is requested.
Do you have an suggestion what the base file changes toolbar button icon should show?
Do you know that you can open the base-file changes from the Conflict Solver?
The Journal focuses on the current branch, its remote branch and one additional (auxiliary) branch. This is a very task-orientated view. Useful improvement suggestions that don't turn it into a fully fledged log are welcome (as separate request, please).
Customer support service by UserEcho
I've implemented that because it offers a quicker way to access certain commands/command variants. Except of OS X (which uses a native toolbar implementation) the dropdown menus are not easily triggerable by accident (small click area), but rather intended to be shown on long click.