Re: importing cvs logical modules

From: Junio C Hamano <junkio@cox.net>
Date: May 25, 2006, 05:01 UTC
Message-ID: <7vslmyzoit.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <93c3eada0605242148u4656bc31p96d84a16703f0fe0@mail.gmail.com>

"Geoff Russell" <geoffrey.russell@gmail.com> writes:

Show 7 quoted lines

> I'd like to make 1 git repository Progs with xxxx and yyyy as child trees.
>
>           Progs/.git
>           Progs/xxxx
>           Progs/yyyy
>
> Does this sound useful to anyone else, or is it already possible?

I would do it like this:

           Progs/.git
           Progs/xxxx/.git
           Progs/yyyy/.git

I do not know what you have in Progs/ hierarchy -- if it is just scaffolding to house subdirectories and nothing else you may not even need Progs/.git repository.

This is a very useful and handy structure, and you do not need any tool support once you have these as separate repositories. If you want a single distribution point, you can push from these separate repositories into separate branches of a single distribution point repository [*1*].

One potential disadvantage is that you would not get revision linkage between these "modules", but not having tight linkage is the point of modular structure, so depending on your workflow it probably may not matter.

[Footnote]

*1* In fact, my git working area has the "master", "next" or "pu" branch checked out in /path/to/work/area/git (and the repository is in /path/to/work/area/git/.git directory), and I check out the "todo" branch in /path/to/work/area/git/Meta directory, with /path/to/work/area/git/Meta/.git directory as its repository.