[PATCH 1 of 8] bundle: allow bundle command to use changegroup3 in tests

[Augie Fackler]

On Apr 9, 2017 12:22 PM, "Pierre-Yves David" <pierre-yves.david at ens-lyon.org>
wrote:



On 04/09/2017 01:42 AM, Augie Fackler wrote:

> On Fri, Apr 07, 2017 at 05:19:20PM +0200, Pierre-Yves David wrote:
>
>>
>>
>> On 04/07/2017 04:44 PM, Jun Wu wrote:
>>
>>> Excerpts from Pierre-Yves David's message of 2017-04-07 16:39:03 +0200:
>>>
>>>> Is there any reasons why we can't just have bundle spec to support cg3?
>>>>>>
>>>>>
>>>>> martinvonz reminds me that the treemanifest part is tricky.
>>>>>
>>>>
>>>> You mean that currently, your cg3 bundle does not support treemanifest?
>>>>
>>>> If so, I'm not sure this is a blocker since treemanifest are still
>>>> experimental and already unsupported by 'hg bundle'.
>>>>
>>>
>>> afaik, cg3 is also experimental.
>>>
>>
>> Okay, so it seems fine to not expose it in bundlespec
>>
>> Out of curiosity, any idea of why it is still experimental?
>>
>
> I don't think so.
>

I'm a bit confused from a language perspective.
Are you saying they are no reason for it to stay experimental?


No reasons that I know of to keep the format experimental.



There are still some performance nasties that I need
> to chase down in narrowhg that *might* turn out to be a treemanifest
> problem, but I think it's far more likely to be a "matchers are slow"
> problem.
>
> It's fine with me if we want to remove the experimental label - I
> think greg was interested in this for Mozilla reasons anyway...
>


Cheers,

-- 
Pierre-Yves David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20170409/1077b391/attachment.html>