Re: With big repos and slower connections, git clone can be hard to work with
- From
- ellie <el@horse64.org>
- Date
- Jun 8, 2024, 20:16 UTC
- Message-ID
- <15611436-01a4-4df5-a8a6-240e502128e4@horse64.org>
- In-Reply-To
- <xmqq8qzfcl98.fsf@gitster.g>
(I'm probably not the person to answer fully. But I can say HTTPS Git clones from GitHub don't ever resume for me, if that's informative.)
On 6/8/24 9:00 PM, Junio C Hamano wrote:
Show 12 quoted lines
> Jeff King <peff@peff.net> writes: > >> One strategy people have worked on is for servers to point clients at >> static packfiles (which _do_ remain byte-for-byte identical, and can be >> resumed) to get some of the objects. But it requires some scheme on the >> server side to decide when and how to create those packfiles. So while >> there is support inside Git itself for this idea (both on the server and >> client side), I don't know of any servers where it is in active use. > > Didn't the bundle URL work originate at GitHub? I thought this use > case was a reasonable match to the mechanism. >