Re: RFC: Subprojects

From: Petr Baudis <pasky@suse.cz>
Date: Jan 23, 2006, 00:50 UTC
Message-ID: <20060123005056.GV28365@pasky.or.cz>
In-Reply-To: <7vek37rj83.fsf@assigned-by-dhcp.cox.net>

Dear diary, on Mon, Jan 16, 2006 at 09:49:48PM CET, I got a letter where Junio C Hamano <junkio@cox.net> said that...

Show 11 quoted lines

>    We could introduce "bind the rest" to make write-tree write
>    out a tree that contains only the containing project part and
>    not any of the subproject part (e.g. Makefile, README and
>    src/ but not linux-2.6/ nor gcc-4.0/ in the earlier example).
>    Essentially the contents of such a tree object would be the
>    same as what "gitlink" approach would have had for the
>    containing project in the index file, minus "gitlink" entries
>    themselves).  This is not so surprising, because the missing
>    information "gitlink" approach recorded in the tree object
>    itself is expressed on "bind" lines in the commit object with
>    this approach.

Now, I must have missed the obvious again, but what is the point in having the write-tree --exclude stuff? My impression (also from your later mail in this thread) is that now the moment you introduce any binds, your top-level development changes to "two-tiered" - the top-level project and the meta-project holding it all together. I'd say that's pretty confusing and I don't see big gain in this; the simplicity of the original proposal was a lot more appealing.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Of the 3 great composers Mozart tells us what it's like to be human,
Beethoven tells us what it's like to be Beethoven and Bach tells us
what it's like to be the universe.  -- Douglas Adams