[PATCH 3 of 3] singlehead: introduce special handling of closed heads

Pierre-Yves David pierre-yves.david at ens-lyon.org
Wed Sep 25 11:54:35 EDT 2019



On 9/25/19 5:29 PM, Pulkit Goyal wrote:
> On Wed, Sep 25, 2019 at 2:17 PM Pierre-Yves David
> <pierre-yves.david at ens-lyon.org> wrote:
>>
>> # HG changeset patch
>> # User Pierre-Yves David <pierre-yves.david at octobus.net>
>> # Date 1569409166 -7200
>> #      Wed Sep 25 12:59:26 2019 +0200
>> # Node ID af71efbe73e62e427eeb559923057f950530fe40
>> # Parent  ddbb9bccf64e004e6e7ee5912b701c732f8a4435
>> # EXP-Topic enforce-single-head
>> # Available At https://bitbucket.org/octobus/mercurial-devel/
>> #              hg pull https://bitbucket.org/octobus/mercurial-devel/ -r af71efbe73e6
>> singlehead: introduce special handling of closed heads
>>
>> Until now, the experimental option `single-head-per-branch` was also refusing
>> closed heads. The logic is now ignoring them by default and a suboption have
>> been added to refuse them too `single-head-per-branch:account-closed-heads`.
>>
>> diff --git a/mercurial/configitems.py b/mercurial/configitems.py
>> --- a/mercurial/configitems.py
>> +++ b/mercurial/configitems.py
>> @@ -645,6 +645,9 @@ coreconfigitem('experimental', 'server.s
>>   coreconfigitem('experimental', 'single-head-per-branch',
>>       default=False,
>>   )
>> +coreconfigitem('experimental', 'single-head-perf-branch:account-closed-heads',
> 
> s/perf/per in flight

ha thanks, I must have spend too much time looking a perf stuff recently.

That said, this means the suboption logic does not triggers devel 
warning :-/


-- 
Pierre-Yves David


More information about the Mercurial-devel mailing list