Re: Submodule object store

["Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>]

Hallo again,

Uwe Kleine-König wrote:
> > I want to be able to list all objects which are not reachable in the
> > object store, without traversing all submodules at the same time.
> > The only way I can think of to achieve this is to have one separate
> > object store per submodule and then do the traversal per submodule.
> I might have understood something wrongly, but to list objects that are
> not reachable you need to traverse all trees anyhow, don't you.  
> 
> Then how big is the difference between a directory and an submodule?
> I'd expect it's not so big if the submodules included in different
> revisions of the supermodule share most of their history.  Of course you
> need to exploit that.  Thinking again that might be the problem?
I didn't look at the code, but an other issue might be:

If you separate the odbs e.g by the pathname of the subproject, what
happens if I choose to move the linux kernel in my embedded Linux
project from /linux to /kernel/linux?

Or maybe worse:  If I currently track the Kernel in a tree (because of
git lacking submodule support) and switch to submodule.  Then
linux/Makefile has to exist in both the supermodule's and the
submodule's odb.

Best regards
Uwe

-- 
Uwe Kleine-König

http://www.google.com/search?q=30+hours+and+4+days+in+seconds