What is the difference between running "git mv" versus just "mv"
git
Solution
Since you have tagged the question with different SCM products and not just `git` I'm answering this in a more general way.
Each source control system tracks different information about files. In Mercurial, for instance, moves are tracked, so that - along with deletion and addition of the renamed file it also stores information about that being a rename, and which file it has been before.
Also, when deleting files, one usually needs to remove it from SCM as well (sometimes also called forgetting).
So generally speaking the SCM file operation commands do update the file system along with the operations needed for the SCM to track this change.
Problem
What is actual difference in results when it comes to source control systems, between running a command like: ``` git mv <src> <dest> # see: https://git-scm.com/docs/git-mv ``` versus a "lower" level command like ``` mv <src> <dest> ``` is there any difference in the result from a version/source control system's perspective? Or anything/anyone's perspective? The same goes for other git commands like `git rm`. `I just want to know what difference it makes between running the git functions versus bash functions, or whatever.`