[PATCH 3 of 5 evolve-ext] prune: add --descendants for pruning entire subtrees

Matt Harbison mharbison72 at gmail.com
Thu Mar 19 21:00:18 CDT 2015


On Thu, 19 Mar 2015 21:36:57 -0400, Durham Goode <durham at fb.com> wrote:

>
>
> On 3/19/15 6:32 PM, Matt Harbison wrote:
>> On Thu, 19 Mar 2015 21:14:28 -0400, Durham Goode <durham at fb.com> wrote:
>>
>>> # HG changeset patch
>>> # User Durham Goode <durham at fb.com>
>>> # Date 1426787637 25200
>>> #      Thu Mar 19 10:53:57 2015 -0700
>>> # Node ID 0a4343392b3358584bd16e7b7f15e9c2264c9c8b
>>> # Parent  22e9be40a47d397339c4d5a5ea7c82131d72d889
>>> prune: add --descendants for pruning entire subtrees
>>
>> Doesn't '-r rev::' do the same thing?  I don't have a subtree I want to  
>> prune handy, but based on passing the same revset to log, it prints  
>> what I would expect --descendants would operate on.
>>
>> --Matt
> Yea, it does but we're in the process of making the evolve UI easier for  
> users to pick up, and making it able to act like strip without having to  
> know the revset syntax is useful.  I don't expect the prune UI to remain  
> fixed, so we can come back here and clean up as we get more feedback.

OK, that makes sense.

On the subject of making prune more user friendly, I've done this a couple  
of times:

   $ hg kill <rev> -s <rev2> <rev3>

thinking it would mark 2 and 3 as successors.  Phases saved me both times,  
but the error message misdirected me into thinking I ran into a bug,  
instead of forgetting the '-s'.  I can't think of any hg command when an  
option can be specified, followed by a list of revs, so I have no idea  
where I got the impulse to do that.  But I suspect others might run into  
it too, and there's no official undo for obsolete that I'm aware of.  Is  
there some way to force '-r' to be used with this command?

--Matt


More information about the Mercurial-devel mailing list