From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Thu, 12 Jan 2006 04:46:09 GMT
Subject: Re: RFC: Subprojects
Message-ID: <46a038f90601112046u13d7075dsc2108111e2462152@mail.gmail.com>
In-Reply-To: <200601120919.08354.lan@ac-sw.com>

On 1/12/06, Alexander Litvinov <lan@ac-sw.com> wrote:
> On Wednesday 11 January 2006 21:58, Simon Richter wrote:
> > Hello,
> >
> > one thing that I have been missing so far in all SCM systems apart from
> > CVS (and there it's just coincidence) is the ability to include a
> > project as part of a bigger project.
>
> 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?

cheers,


martin