Submitter | phabricator |
---|---|
Date | June 10, 2019, 10:37 p.m. |
Message ID | <differential-rev-PHID-DREV-h5lx4ggsbuedgt2fxt22-req@phab.mercurial-scm.org> |
Download | mbox | patch |
Permalink | /patch/40417/ |
State | Superseded |
Headers | show |
Comments
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