Re: RFC: Subprojects

From: Alexander Litvinov <lan@ac-sw.com>
Date: Jan 12, 2006, 05:25 UTC
Message-ID: <200601121125.33696.lan@ac-sw.com>
In-Reply-To: <46a038f90601112046u13d7075dsc2108111e2462152@mail.gmail.com>

On Thursday 12 January 2006 10:46, Martin Langhoff wrote:

Show 13 quoted lines

> > I really miss this feature. This is the last stopper for moving from CVS
> > to git for out project.
>
> What about using nested checkouts? They work great with git as-is,
> just add an .gitignore file.
>
> As Linus points out, there are many good reasons why a top-level
> commit should _not_ commit the nested subproject. And once you are
> observing that rule, what's left then? git status and git diff <HEAD>
> can show an aggregate of top-level and nested subprojects, but that's
> ease-of-use -- not something only.
>
> What is your show stopper?

I would agree to make separate commits for each sub project.

1. I need to have ability to make tags, branches thru all subprojects.
2. Update (pull) sould update each subproject, it is hard to update them by 
hands.
3. The need of some sort of checkout script (can be solved by storing this 
script in base project, but it would be much nicer allow git fetch all 
subprojects)

Nothing else I can imagine.