# HG changeset patch
# User Pierre-Yves David <pierre-yves.david@octobus.net>
# Date 1534846691 -7200
# Node ID d8b0086a11a1c1b4cafa91c18630033d3b356c38
# Parent  ec57afdbe054a1df06f706742680fe94aef3925f
prune: no longer consider dropping --biject

Field testing show it save people one wrong call often enough that it is worth
keeping.

diff -r ec57afdbe054 -r d8b0086a11a1 hgext3rd/evolve/cmdrewrite.py
--- 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