Your comments
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.
To be more specific: you are requesting an additional "will be handled by LFS" indicator for untracked files in the Files view? Note that there is already a similar request for tracked files:
SmartGit 22.1 will show the merge base in the Commit view.
This option will be present in upcoming version 22.1 Preview.
Customer support service by UserEcho
> 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.