Re: Submodule object store
- From
Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de>
- Date
- Mar 27, 2007, 19:42 UTC
- Message-ID
- <20070327194233.GA28229@informatik.uni-freiburg.de>
- In-Reply-To
- <Pine.LNX.4.64.0703271124590.6730@woody.linux-foundation.org>
Hello Linus,
Linus Torvalds wrote:
Show 12 quoted lines
> On Tue, 27 Mar 2007, Uwe Kleine-König wrote: > > > > embeddedproject$ git ls-tree HEAD | grep linux > > 040000 commit 0123456789abcde0... linux-2.6 > > > > (or how ever you save submodules). Then you might have to duplicate the > > objects of linux-2.6, because they are part of both histories. > > No they are not. Unless you do it wrong. > > The *only* object that is part of the superproject would be the tree that > *contains* that entry itself.
Yes, I got that. I think my concern is still valid, so probably I was just unable to phrase it explicitly. So I retry:
In the state above (i.e. linux-2.6 being a commit) the superproject's odb doesn't necessarily needs the object 0123456789abcde0, right. But the commit before that had linux-2.6 being a tree. And in that state linux-2.6/Makefile has to be in the superproject's odb. So if you choose the save the objects of submodules in a different odb, linux-2.6/Makefile has to be in both of them. I agree with the things you said afterwards, but they don't match the issue I wanted to point out.
Best regards Uwe
-- Uwe Kleine-König http://www.google.com/search?q=2004+in+roman+numerals