I asked about writing a portion of resumable clone about two months ago,
and decided to write the prime-clone program. I got bogged down by work
in the time since and have just gotten started working on the feature maybe
a week or two ago.
Anyway, I sent along a very rough version of prime-clone, with endpoints added
for http-backend and daemon. My hope is to use this as a jumping-off point to
create the prime_clone method for the client transport for .pack files only,
but I wanted to get some feedback about the configuration as I move along, as
I'm sure there are a lot of design considerations I missed, and I want to keep
this as easily extensible to the other types as possible.
Apologies for not keeping everyone in the loop. I should be working on this
more actively from this point onwards.
[PATCH 1/2] Resumable clone: create git-prime-clone (Draft)
[PATCH 2/2] Resumable clone: add endpoints for prime clone (Draft)
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email] More majordomo info at http://vger.kernel.org/majordomo-info.html
Create a bare-bones version of git-prime-clone, which returns the
location of an alternate resource specified by the server that the
client should fetch and build before returning to perform an incremental
At this point, no validation is performed of the file's existence, the
file's validity as a fully connected archive, or its correspondence
to the specified resource type in .git/config.
Makefile | 1 +
prime-clone.c | 87 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 88 insertions(+)
create mode 100644 prime-clone.c