Will be fixed for 22.1 Preview 3.

Subtrees are just remotes, hence fetching is straight-forward. I have updated the docs. Given the remaining operations (especially merge), does this make the workflow clear now? If not, please also consider to Propose Changes to the docs directly.

> Rename the menu item to Rename/Move to make it clear for beginners that it covers both

That sounds helpful. We will change this to "Move or Rename" for 22.1.

You can already move files using Rename, so we most likely won't add another redundant Move operation. Also, you have mentioned "move a file already under version control to a newly created sub-directory", hence I was assuming that you have already discovered the move functionality in the Rename ... what I can confirm is that Rename does not yet support to move to an untracked sub-directory. Hence, for me the most reasonable and smallest change to address this RFE is to change the existing Rename functionality to support that. Do you agree?

It's actually a smart decision of Git's design and will most likely never be changed. You may find more information here:

https://stackoverflow.com/questions/115983/how-can-i-add-a-blank-directory-to-a-git-repository

Which exact functionality would you use here, supposing that the directory already exists?

Git does not support to manage empty folders.

I guess you are referring to Rename? I have updated the title correspondingly.

Implemented for upcoming 22.1 preview 1: all parents of the selected commit plus its entire first-parent history will be highlighted on HiDPI. For LoDPI we have not yet decided on the default, but at least there will be Low-Level Property "log.graph.highlightSelectionAtDpiScaling" to enable this manually.