[PATCH 4 of 5 V2] histedit: add execute function (issue4036)

[Olle]

On Thu, Mar 6, 2014 at 8:41 PM, Augie Fackler <raf at durin42.com> wrote:

>
> On Mar 6, 2014, at 1:52 PM, Olle <olle.lundberg at gmail.com> wrote:
>
> It seems reasonable, it might be confusing for git refugees though. Not
> that we try to cater everything for them. Just a heads up. I'm up for
> changing it, if filterrevs are prefered. But then we'll get two commands
> (histedit and filterrecs) doing more or less the same thing, history
> editing, except one is automatic. Don't know how if that will be confusing.
>
>
> Place git out of your mind for the moment.
>
> The way I'm thinking about this is that there's interactive history
> rearrangement and editing (histedit) and pseudo-automated reformatting of
> commits without reordering (filter revs). Does that seem like a reasonable
> split?
>

Yeah, I'd like to place git as far as way as possible. And I can very much
agree that it makes sense to split them up. The use case would then become:

hg histedit deadbeef
and then

hg filterrevs deadbeef:cafebabe "everything else as a command?"
or perhaps:
hg filterrevs deadbeef:cafebabe --cmd "cool command here"


-- 
Olle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-devel/attachments/20140306/dd913159/attachment-0002.html>