[PATCH 1 of 8] bundle: allow bundle command to use changegroup3 in tests
Jun Wu
quark at fb.com
Fri Apr 7 10:14:42 EDT 2017
Excerpts from Pierre-Yves David's message of 2017-04-07 16:07:08 +0200:
>
> On 04/07/2017 04:08 AM, Jun Wu wrote:
> > # HG changeset patch
> > # User Jun Wu <quark at fb.com>
> > # Date 1491523318 25200
> > # Thu Apr 06 17:01:58 2017 -0700
> > # Node ID 3d62d68ed4245359b5ae5b6b6c1959a15ffa84e9
> > # Parent 45761ef1bc935b1fab74adccf2541ef854b1c2eb
> > # Available At https://bitbucket.org/quark-zju/hg-draft
> > # hg pull https://bitbucket.org/quark-zju/hg-draft -r 3d62d68ed424
> > bundle: allow bundle command to use changegroup3 in tests
> >
> > Since bundle2 writes changegroup version, we can just reuse the bundle2
> > format for changegroup3.
> >
> > This won't enable the bundle command to write changegroup3 in the wild,
> > since exchange.parsebundlespec only returns changegroup2.
>
> Is there any reasons why we can't just have bundle spec to support cg3?
martinvonz reminds me that the treemanifest part is tricky.
>
> The usual way to go here is:
> 1) add a way to specify the bundle content you want as a bundlespec
> 2) automatically upgrade to the minimal subset we need to not loose
> information when special feature is used. (in your case cg3)
>
More information about the Mercurial-devel
mailing list