> From: Ryan Hodson <hodson.r...@gmail.com>
> If you're not looking for a submodule, you can just move the tracked files
> into a subdirectory with 'mv' or through your file browser. Then run 'git
> add .' in the project root and Git will figure out the file renames on its
> own. The 'git mv' command can be used to the same effect.
OK, so it seems that when you move files around, and then tell git to
notice that, git will automagically figure out what the moves were.
The O'Reilly book wasn't clear on that. (Nor did it explain how git
can distinguish a move from file that just happens to have the same
Another question is this: I believe that the complete repository and
its status lives in the .git directory. So if I move ./.git to ../.git,
it has the same effect as if I moved all the normal files into a
subdirectory of ".". Is that correct?