Mercurial > evolve
changeset 4708:dcdd2b3ce52c stable
evolve: further clarify that update is performed only when requested
Text further modified by Pierre-Yves David and Anton Shestakov.
author | kevpeng@google.com |
---|---|
date | Thu, 04 Jul 2019 17:32:58 +0200 |
parents | fcecbb1261f2 |
children | 24e83f51ffc2 |
files | hgext3rd/evolve/evolvecmd.py |
diffstat | 1 files changed, 2 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/hgext3rd/evolve/evolvecmd.py Mon Jul 01 19:15:57 2019 +0530 +++ b/hgext3rd/evolve/evolvecmd.py Thu Jul 04 17:32:58 2019 +0200 @@ -1534,9 +1534,8 @@ If so, evolve rebases that changeset. If not, evolve refuses to guess your intention, and gives a hint about what you might want to do next. - Any time evolve creates a changeset, it updates the working copy to the new - changeset. Using ``--update`` will make evolve perform an update after any - successful evolve operation. + When ``--update`` is used, successful evolve operations update the + working directory to the newly created changesets. Automatic mode only handles common use cases. For example, it avoids taking action in the case of ambiguity, and it ignores orphan changesets that are