3That changesets is a pure improvement, over the previous state, so I
took it. (I changed 'evolve:' into 'prune:' in the summary)
Can you followup with a series taking timeless input in account and
with some sort of document/pointing at the 'allowunstable' option?
On 12/12/2016 03:41 AM,
I'm not going to stop this from going in, it's definitely an improvement.
>> @@ -3299,7 +3301,8 @@
>> head = repo[heads.first()]
>> if _disallowednewunstable(repo, revs):
>> raise error.Abort(_("cannot fold chain not ending with a head "\
>> -"or
Shouldn’t we mention the config in a hint message?
On 11/25/16, 12:28 PM, "Mercurial-devel on behalf of Mateusz Kwapich"
wrote:
LGTM, I suppose that timeless may also want to review it before it's
queued.
LGTM, I suppose that timeless may also want to review it before it's
queued.
Excerpts from Pulkit Goyal's message of 2016-11-24 23:13:48 +0530:
> # HG changeset patch
> # User Pulkit Goyal <7895pul...@gmail.com>
> # Date 1479915042 -19800
> # Wed Nov 23 21:00:42 2016 +0530
> # Node ID
# HG changeset patch
# User Pulkit Goyal <7895pul...@gmail.com>
# Date 1479915042 -19800
# Wed Nov 23 21:00:42 2016 +0530
# Node ID 920d5946d13339d9cf4828f678fb55063cd8
# Parent cb2bac3253fbd52894ffcb4719a148fe6a3da38b
evolve: improve error message if unstable changes are disallowed
I