Re: Submodule object store

[Linus Torvalds <torvalds@linux-foundation.org>]

On Tue, 27 Mar 2007, Linus Torvalds wrote:
> 
> In other words, I don't think that's an argument for or against sharing 
> the object database. You should *always* be able to share the object 
> database by setting GIT_OBJECT_DIR if you want (or by using alternates). 
> But that's independent of whether you are a sub/supermodule..

In fact, I suspect that you might well have a situation where there are 
more objects to be shared "across" superproject boundaries than within 
them.

For example, say that I'm a mirror site, and I mirror two different 
distributions, both of which use superprojects (but *different* 
superprojects!) to track their distro stuff.

Obviously, the top-level setup is likely totally different, and they 
probably differ a bit in which subprojects they have too, but in many 
cases, those two *different* superprojects will have subprojects that 
could often share 99% of all their objects not within the superproject, 
but individually *across* superprojects.

So you would not want to have a object store that is tied to the 
superproject, but you might well want to have each superproject share the 
object store for the subprojects that they have in common. The "kernel" 
subproject in the "ubuntu" superproject might want to share the object 
store for the "linux-2.6" subproject in the Fedora 7 superproject.

(Similarly, there migh be sharing with totally *individual* projects, ie 
you might want to make both just have an alternate that points 
directly to the "official" tree that is in neither of the two 
superprojects and that I maintain separately).

		Linus