Help designing the evolve UI

Colin Caughie c.caughie at gmail.com
Thu Apr 17 08:52:29 CDT 2014


On 04/17/2014 2:14 AM, Angel Ezquerra wrote:
>
>
> El 17/04/2014 04:28, "Pierre-Yves David" 
> <pierre-yves.david at ens-lyon.org 
> <mailto:pierre-yves.david at ens-lyon.org>> escribió:
> >
> >
> >
> > On 04/16/2014 09:47 PM, Greg Ward wrote:
> >>
> >> +1 to "prune": "kill" is a bad name. I think "obsolete" can
> >> technically be used as a verb... but let's not. "prune" is good.
> >
> >
> > `kill` is a terrible terrible terrible subcommand name.
> >
> > I figured that out the day I forgot the `hg` part of `hg kill -1`...
> >
> > The prune alias appear in the next hour as the official name.
> >
> > Prune get along nicely with "graft"
> >
> > --
> > Pierre-Yves
>
> One of my biggest issues with the current evolve UI is that a plain 
> "hg evolve" only evolves one revision. This surprised me a lot when I 
> first tried the evolve command and it still annoys me every time I use it.
>
> The reason is that I relate "hg evolve" to "hg rebase" and "hg rebase" 
> rebases all until it finds a conflict. So I think that for 
> consistency's sake it would be best if hg evolve evolved all. There 
> cities be a flag to evolve a single revision instead.
>
+1. As the guy who has to explain to the rest of my team how to do these 
things, this is definitely one of the "why did they do it that way" 
questions I'll be asked when I finally move them all over to evolve.

With regard to the proposed "reorder" command, and the suggestion that 
histedit can be completely replaced: to be honest I can't think of many 
ways to do that that would be more user friendly and intuitive than 
histedit. I can imagine scenarios where it would be handy to be able to 
do the same thing from the command line, but in practice I think I'd 
always want to use the interactive version.

Colin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20140417/77719de1/attachment.html>


More information about the Mercurial-devel mailing list