hoi :)
On Fri, Dec 01, 2006 at 09:04:37PM +0000, Andy Parkins wrote:
quoted
It may be possible to use two object stores and still do the common
object traversal but I do not think that gives you any benefits.
There is one benefit - you can git-clone the submodule just as you
would if it were not a submodule. In fact, from the submodule's point
of view it knows nothing about the supermodule.
The submodule repository obviously has to able to reach all its objects.
This is easily doable with the shared object database.
So you can already clone the submodule standalone.
I'm going to guess by reachability analysis, you mean that the
submodule doesn't know that some of it's commits are referenced by the
supermodule. As I suggested elsewhere in the thread, that's easily
fixed by making a refs/supermodule/commitXXXX file for each
supermodule commit that references as particular submodule commit.
I wouldn't call this "easily".
--
Martin Waitz