On Sun, Aug 05, 2012 at 11:38:12AM +0200, Michael Haggerty wrote: > I have some other crazy ideas for making the concept even more powerful: > > * Support remote alternate repositories. Local repository obtains > missing objects from the remote as needed. This would probably be > insanely inefficient without also supporting... > > * Lazy copying of "borrowed" objects to the local repository. Any > object fetched from the alternate object store is copied to the local > object store. > > Together, I think that these two features would give fully-functional > shallow clones.
You might be interested in looking at my rough (_very_ rough) experiment with object db "hooks": https://github.com/peff/git/commits/jk/external-odb The basic idea is to have helper programs that basically have two commands: give a list of sha1s you can provide, and fetch a specific object by sha1. That's enough for the low levels of git to fall-back to a helper on an object lookup failure, and copy the object to a local cache. Managing the cache could be done externally by helper-specific code. Sorry, there's no documentation on the format or behavior, and most of the changes are in one big patch. If you're interested and find it unreadable, I can try to clean it up. -Peff -- 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
