Mercurial Mercurial > pub > hg > evolve / changeset
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | raw | zip | gz | bz2 | help
Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
prune: no longer consider dropping --biject stable
authorPierre-Yves David <pierre-yves.david@octobus.net>
Tue, 21 Aug 2018 12:18:11 +0200
branchstable
changeset 3986 d8b0086a11a1
parent 3985 ec57afdbe054
child 3987 b802003ffb50
prune: no longer consider dropping --biject Field testing show it save people one wrong call often enough that it is worth keeping.
hgext3rd/evolve/cmdrewrite.py file | annotate | diff | comparison | revisions 
--- a/hgext3rd/evolve/cmdrewrite.py	Tue Aug 21 12:13:01 2018 +0200
+++ b/hgext3rd/evolve/cmdrewrite.py	Tue Aug 21 12:18:11 2018 +0200
@@ -970,8 +970,7 @@
     You can use the ``--biject`` option to pair the pruned precursor
     and successor changesets. This is commonly useful for resolving
     history divergence, or when someone else does edits history
-    without obsolescence enabled. (This option may be removed in a
-    future release with the functionality provided automatically.)
+    without obsolescence enabled.
 
     If you specify multiple revisions in ``-s/--succ``, you are recording a "split" and
     must acknowledge it by passing ``--split``. Similarly, when you prune multiple
evolve