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.

Hope that helps.

On Nov 28, 2012 1:13 PM, "Dale R. Worley" <wor...@alum.mit.edu> wrote:
> I am just beginning to use git.  I've read the O'Reilly book (by
> Loeliger and McCullough), and (unexpectedly) it didn't give me a clear
> view of some of the messier aspects of git.  So as a first question,
> I'd like to know if anyone knows of an exposition that gives a clear
> and accurate description of the logical structure of git repositories
> and git operations.
> As a second question, consider a situation I am now in.  I've been
> using git to maintain a repository of a directory.  I now want to
> start tracking all the files in the *parent* of that directory,
> continuing the history of all the files that are now in the
> repository.  I know how to use Subversion to do this, with one or two
> commands I can move the repository files into a subordinate directory
> in the repository.  But what is the correct way to do this in git?
> Thanks,
> Dale
> --


Reply via email to