From: "Junio C Hamano" <gitster@xxxxxxxxx>
Sent: Wednesday, March 02, 2016 8:41 AM
Josh Triplett <josh@xxxxxxxxxxxxxxxx> writes:
If you clone a repository, and the connection drops, the next attempt
will have to start from scratch. This can add significant time and
expense if you're on a low-bandwidth or metered connection trying to
clone something like Linux.
For this particular issue, your friendly k.org administrator already
has a solution. Torvalds/linux.git is made into a bundle weekly
with
$ git bundle create clone.bundle --all
Isn't this use of '--all' a bit of oversharing? I had proposed a doc patch
to the bundle manpage way back (see $gmane/205897) to give the
user that example, but it wasn't accepted as it was thought wrong.
" I also think "--all" is a bad advice for another reason. Doesn't it
shove refs from refs/remotes/* hierarchy in the resulting bundle?
It is fine for archiving purposes, but it does not seem to be a good
advice to create a bundle to clone from."
Perhaps the '--clone-bundle' (or maybe'--bundle-clone') option from
$gmane/288222 [PATCH] index-pack: --clone-bundle option 2016-03-03 maybe a
suitable new <rev-list-arg> to get just the right content?
and the result placed on k.org CDN. So low-bandwidth cloners can
grab it over resumable http, clone from the bundle, and then fill
the most recent part by fetching from k.org already.
The tooling to allow this kind of "bundle" (and possibly other forms
of "CDN offload" material) transparently used by "git clone" was the
proposal by Shawn Pearce mentioned elsewhere in this thread.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html