https://bz.mercurial-scm.org/show_bug.cgi?id=6386
Bug ID: 6386
Summary: metaedit should trigger evolve --all
Product: Mercurial
Version: default branch
Hardware: PC
OS: Linux
Status: UNCONFIRMED
Severity: feature
Priority: wish
Component: evolution
Assignee: bugzi...@mercurial-scm.org
Reporter: friedric...@gmx.de
CC: mercurial-devel@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
Python Version: ---
Metaedit is really convenient to refactor the recent commit messages of a topic
stack like
hg metaedit s2
But after that I need to run
hg evolve
manually which I dont like because metaedit did not introduce any potential
conflicts. Thats why I think it should be save to (from the user perspective)
to run `evolve --all` after metaedit automatically.
The only objection against this feature request is the potential marker
explosion explained by Pierre-Yves David last year:
https://www.mercurial-scm.org/pipermail/evolve-testers/2019-May/000389.html
Is there any progress about this marker-explosion issue? From my understanding
it could be very easy if the topic extension is used: just delete all markers
(on client and server) when the topic is published. What do you think?
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
