record and crecord: proposal to merge into core

Gregory Szorc gregory.szorc at gmail.com
Tue Mar 10 23:09:26 CDT 2015


On Mon, Mar 9, 2015 at 10:21 AM, Laurent Charignon <lcharignon at fb.com>
wrote:

>
>      Step 3 Add interactive selection to other existing command
>           - Any suggestion here?
>


A question that I semi-frequently get is how to "split" a commit. The
ability to use the "edit" action in histedit combined with "hg record" is
somewhat arcane to discover. I wonder if there is room for a dedicated "hg
split <rev>" command that does the equivalent of:

1. update to requested revision
2. "uncommit" all changes made by the commit (rough equivalent of "hg
uncommit" from evolve)
3. Allows you to use "hg record" until status reports no modifications
4. Automatically rebases children changesets when done

This is essentially "hg histedit" with the "edit" action on 1 changeset.
Perhaps we could implement "hg split" in terms of a histedit recipe? Maybe
we should be moving histedit's "action processing" into core as well? I
know I've wanted to do things in extensions like rewrite commit messages in
a changeset in the middle of the stack. It's quite tedious. </scope bloat>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20150310/8816ab5e/attachment.html>


More information about the Mercurial-devel mailing list