Josef Weidendorfer <Josef.Weidendorfer@xxxxxx> writes: > On Tuesday 27 March 2007, Junio C Hamano wrote: >> Martin Waitz <tali@xxxxxxxxxxxxxx> writes: >> >> > For submodules I currently use <parent>/.git/objects/module/<submodule>/ >> > to store the objects belonging to the submodule. >> >> I was not following the gitlink discussion closely, but what is >> the motivation behind this separation of the object store? > > The separation issue is about scalability of submodules, and not > directly about gitlink. Unless you are thinking about rsync of object store, it is not clear what "scalability of submodules" has to do with having separate object database. The issue I recall from earlier discussion on scalability of submodules was about the direct placement of commit objects in supermodule trees (which would force fetching in supermodule to drag in all submodules even when the "integration" or "build infrastructure" person does not want to have submodules pulled). But I think that is an issue of the definition of connectivity. It should be orthogonal to the issue of how object store is laid out, shouldn't it? - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html