> - By design, the borrowed object store MUST not ever lose any
> object from it, as such an object loss can corrupt the borrowing
> repositories. In theory, it is OK for the object store whose
> objects are borrowed by repositories to acquire new objects, but
> losing existing objects is an absolute no-no.
> In practice, this means that users who use "clone -s" to make a
> new repository can *never* prune the original repository without
> risking to corrupt its borrowing repository [*1*].
Given your example of /git/linux.git being a clone of Linus' repository,
cloning a related repository using it as --reference:
$ cd /git
$ git clone --reference /git/linux.git git://k.org/linux-next.git mine
Wouldn't it be by far a less intrusive alternative to do the following (in the
clone step above):
- create the file /git/linux.git/objects/borrowing/_git_mine (This is where we
This file would hold a packed-ref list of HEADs from the /git/mine clone of
_git_mine here is slash-stripped version of the destination path. Maybe the
packed-ref format could also be extended by a single line containing a full
path to the foreign repository.
- On every update-ref to /git/mine, update the 'borrowing' refs in
- On any maintenance on /git/linux.git (gc, prune, repack, etc.) consider refs
in the packed-refs at objects/borrowing to be valid references.
If packed-ref format was adopted like stated above, we could stat() here if
this directory still exists and error out if it doesn't (In this case the
user should tell us if she moved or removed the clone).
Any alternatives for looking up the packed-refs list for borrowing would also
be doable; i.E. putting the list of valid borrowing-packed-refs-files into the
config file (as opposed to lookup $GIT_DIR/objects/borrowing above).
Putting this list into the config file would eliminate need for the packed-ref
format change and give the user the ability to maintain her clones with well-
known command 'git config'
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html