Patchwork D6507: rebase: tweak description of inmemory working even w/ dirty working dir

login
register
mail settings
Submitter phabricator
Date June 12, 2019, 4:45 p.m.
Message ID <e9e89d23e49557577684480c66df8291@localhost.localdomain>
Download mbox | patch
Permalink /patch/40446/
State Not Applicable
Headers show

Comments

phabricator - June 12, 2019, 4:45 p.m.
Closed by commit rHGcda591d2bfe1: rebase: tweak description of inmemory working even w/ dirty working dir (authored by spectral).
This revision was automatically updated to reflect the committed changes.
This revision was not accepted when it landed; it landed in state "Needs Review".

REPOSITORY
  rHG Mercurial

CHANGES SINCE LAST UPDATE
  https://phab.mercurial-scm.org/D6507?vs=15434&id=15457

CHANGES SINCE LAST ACTION
  https://phab.mercurial-scm.org/D6507/new/

REVISION DETAIL
  https://phab.mercurial-scm.org/D6507

AFFECTED FILES
  hgext/rebase.py

CHANGE DETAILS




To: spectral, martinvonz, #hg-reviewers
Cc: mjpieters, mercurial-devel

Patch

diff --git a/hgext/rebase.py b/hgext/rebase.py
--- a/hgext/rebase.py
+++ b/hgext/rebase.py
@@ -850,8 +850,9 @@ 
       singletransaction = True
 
     By default, rebase writes to the working copy, but you can configure it to
-    run in-memory for for better performance, and to allow it to run if the
-    working copy is dirty::
+    run in-memory for better performance. When the rebase is not moving the
+    parent(s) of the working copy (AKA the "currently checked out changesets"),
+    this may also allow it to run even if the working copy is dirty::
 
       [rebase]
       experimental.inmemory = True