[Bug 5317] New: amend -i should uncommit

mercurial-bugs at selenic.com mercurial-bugs at selenic.com
Sat Jul 30 20:46:25 EDT 2016


            Bug ID: 5317
           Summary: amend -i should uncommit
           Product: Mercurial
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: UNCONFIRMED
          Severity: feature
          Priority: wish
         Component: evolution
          Assignee: bugzilla at selenic.com
          Reporter: sphink at gmail.com
                CC: mercurial-devel at selenic.com,
                    pierre-yves.david at ens-lyon.org

Perhaps this couldn't be the default and it requires another flag.

More than 90% of the time when I |amend -i| a change, I want to choose what to
keep from the union of the original change and what's in my working directory.
Right now, I |hg uncommit -a; hg amend -i|. I think I've used amend -i without
uncommitting maybe once.

Mentally, I'm almost always thinking of "updating a committed patch", not
"choosing what to add to a committed patch". Just from muscle memory, probably
what I'd do for the latter is |hg commit -i -m rollme; hg commit -m otherstuff;
hg chistedit|. Which is certainly a long way to go about it, but I am very very
often adding bits and pieces to patches deeper in my current nonpublic stack
anyway, and I have to use chistedit for those. So I'm just used to constructing
fragmentary patches and rolling them into where they need to go. I don't notice
when I'm in the unusual case of being able to directly amend the top patch.

You are receiving this mail because:
You are on the CC list for the bug.

More information about the Mercurial-devel mailing list