Re: Resumable git clone?

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 2, 2016, 17:57 UTC
Message-ID: <xmqqk2lk4vb5.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <20160302164906.GB13732@x>

Josh Triplett <josh@joshtriplett.org> writes:

Show 5 quoted lines

> That does help in the case of cloning torvalds/linux.git from
> kernel.org, and I'd love to see it used transparently.
>
> However, even with that, I still also see value in a resumable git clone
> (or git pull) for many other repositories elsewhere,...

By "transparently" the statement you are responding to meant many things.

"git clone" of course need to be updated on the client side, but things like "git repack" that is run on the server end may start producing extra files in the repository, and updated "git daemon" and/or "git upload-pack" would take these extra files as a signal that the material produced during the last repack is usable for bootstrapping a new clone with "wget -c" equivalent. So even if you are not yet automatically offloading to CDN, such a set of updates on the server side would "transparently" enable the resumable clone for all repositories elsewhere when deployed and enabled ;-)