Re: Submodule object store

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Martin Waitz <tali@xxxxxxxxxxxxxx> writes:

> To make purge and fsck work we have the hard requirement that it
> must be possible to list all objects which belong to one submodule.

I understand you would want to separate the ref namespace, but I
still do not see why you would want to have a separate object
store, laid out in a funny way.  Unless you are thinking about
using rsync to transfer object store, that is.

> And moving the submodule object store into the .git directory of the
> supermodule has several reasons:...

Oh, I am not disputing that.  If you want to use a single object
store for both levels, I think that is a sensible thing to do.
I just do not see the point of segregating submodule objects and
supermodule objects in the single object store you attach to the
supermodule.  After all, any traversal starts from refs, so by
segregating the ref namespace you would limit the extent of the
traversal, no?

-
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]