This is whacky, but another completely different strategy is to introduce remote alternates. If you can allow objects/info/alternates to name a repository that is not on the local disk, we can set the original remote repository we "clone" from as one of the alternates, and teach read_sha1_file() to locally cache objects we read from remote alternates. After such a "shallow clone", the user may want to prime the cache by something like: $ git-rev-list --objects v2.6.14..master | git-pack-objects --stdout >/dev/null before going offline. Obviously you can keep the resulting pack instead of leaving things loose. I am not seriously advocating this yet -- adding calls to http and git transfer machinery in read_sha1_file(), which is as low level as you can go, is not something I have guts to do at the moment. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Wed Feb 01 08:00:05 2006
This archive was generated by hypermail 2.1.8 : 2006-02-01 08:01:16 EST