git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: question about resume support.

From
Kevin Daudt <me@ikke.info>
Date
Feb 22, 2015, 15:53 UTC
Message-ID
<20150222155312.GA7906@vps892.directvps.nl>
In-Reply-To
<20150221200127.4ade03ad@archus>
On Sat, Feb 21, 2015 at 08:01:27PM +0100, drathir87@gmail.com wrote:
Show 25 quoted lines
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Hi... Im wonder there is planned or maybe there is support of resuming
> interrupted git operation e.g. cloning repositories? Not sure about how
> hard that could be to implement, but greatly should decrease of
> bandwidth used by persons with weak network connection...
> -----BEGIN PGP SIGNATURE-----
> 
> iQJ8BAEBCgBmBQJU6NYHXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFMEZBMTE5Mjc5MTM0QTZFNDdGRTk3MEZB
> RUEzMzk3NTlGNjNCMEZDAAoJEK6jOXWfY7D8CXsP/37F3cHNVgrNj+xzeR1H38xQ
> q5zSLNMUYr771gUXBac/p8MfDYlS7gKwRV4Bxhl8AmfH9q28ybj4UFp+5A9u1mKF
> E4rrMJE4mrwf/dOeYHMd4EK7aCFrEl9DVnD6uXlQ+QC6qQ23LyR2WHVX3u1a6EQV
> tsFIuGLh1kBATWt2/Fim60BqI6P3/PX0gB2R+gPdnm5vG3cY5iNSw/UgZUbRNmMa
> QgzBwpxNOTqlJ3GQ9cWgL5CH83VrFmjqHqa8xbVd2ATVaWXTk4pDJFBBafSNJg8s
> RMumCGpWmMYBEtAJY/UgE32F2ms7ravLOY0hj9PCoW0FH+czdI9ZNQ8jvdThMByp
> +6mHqU2SyYoetnBclcgSrOMdkiCivWB7GaOBscA5E1MM3FpQBdJSBrDlq5yhs9WG
> uKhyBpts9+9IdiUPvd4ej4CVXXsE9/FKAEK7+ilr7HsLbRr0vXeAiWA7q+k+Avce
> Ih8nwt9onAM37OH7BoW8va/4g/3yHr9EaYFg7ea9hJYUomVY3l/mIQxeG+KPFZnC
> XnCVAEMSeMujwjIKqHUEWS8RuHOlxS+q8TEZS7caR/8ausondbQuYK4HLsVhiwFZ
> AklwtLBmoIR2yNFn+NKfDOw1RWPsvHSN7yKEQIe+SdUEDDS8QvhfCeKDVSD77ezX
> BpXSPfNLMDYqZNp5f+NB
> =+Bnw
> -----END PGP SIGNATURE-----

While not the best solution, what's currently possible is to provide an initial git bundle that is regularly updated which can be downloaded through other protocols that do provide resumption. Users can use that to setup the repository, and then use the normal git protocol to get the latest updates.

The reason this is not easy to facilitate is that the packs git generates are only generated in-memory. These packs would need to be cached on disk and somehow have a mapping to the user that downloaded that pack. Also there would need to be some kind of way to expire these cached packs. The protocol would need to be updated to indicate a users wants to resume a clone (or fetch) and what parts are still missing, and probably lots of other details I'm missing.

Kevin
Previous: drathir87@gmail.comNext: drathir87
Message 2 of 3 in “question about resume support.”
  1. drathir87@gmail.comFeb 21, 2015
  2. Kevin DaudtFeb 22, 2015
  3. drathir87Feb 25, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.