I'm not really sure what you're looking for with your first question, but
for the second, it sounds like you want submodules/superproject:
On Wed, Nov 28, 2012 at 2: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?