list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <>
To: Shawn Pearce <>
Cc: Stefan Saasen <>,
	Git Mailing List <>
Subject: Re: Git clonebundles
Date: Sun, 5 Feb 2017 17:37:06 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, Feb 4, 2017 at 6:39 PM, Shawn Pearce <> wrote:
> On Mon, Jan 30, 2017 at 11:00 PM, Stefan Saasen <> wrote:
>> Bitbucket recently added support for Mercurial’s clonebundle extension
>> (
>> Mercurial’s clone bundles allow the Mercurial client to seed a repository using
>> a bundle file instead of dynamically generating a bundle for the client.
> ...
>> Prior art
>> ~~~~~~~~~
>> Our proof-of-concept is built on top of ideas that have been
>> circulating for a while. We are aware of a number of proposed changes
>> in this space:
>> * Jeff King's work on network bundles:
>> * Nguyễn Thái Ngọc Duy's work on "[PATCH 0/8] Resumable clone
>> revisited, proof of concept":
>> * Resumable clone work by Kevin Wern:
> I think you missed the most common deployment of prior art, which is
> Android using the git-repo tool[1]. The git-repo tool has had
> clone.bundle support since Sep 2011[2] and the Android Git servers
> have been answering /clone.bundle requests[3] since just before that.
> The bundle files are generated with `git bundle create` on a regular
> schedule by cron.
> [1]
> [2]
> [3]

There is also Junio's work on Bundle v3 that was unfortunately
recently discarded.
Look for "jc/bundle" in:

and previous "What's cooking in git.git" emails.

I am also working on adding external object database support using
previous work by Peff:

that could be extended to support clone bundles.


  reply	other threads:[~2017-02-05 16:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31  7:00 Git clonebundles Stefan Saasen
2017-02-04 17:39 ` Shawn Pearce
2017-02-05 16:37   ` Christian Couder [this message]
2017-02-06 22:16     ` Junio C Hamano
2017-02-07 12:04       ` Johannes Schindelin
2017-02-07 15:34         ` Stefan Beller
2017-02-07 20:54         ` Junio C Hamano
2017-02-08 14:28           ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).