Mercurial > evolve
changeset 3990:566fe891f1ec stable
prune: more human-friendly documentation
The previous help string generally had a highly technical language. I've tried
my best to address that.
| author | Dan Villiom Podlaski Christiansen <dan@magenta.dk> |
|---|---|
| date | Tue, 21 Aug 2018 12:13:28 +0200 |
| parents | b60113460856 |
| children | c63bcff591ea |
| files | hgext3rd/evolve/cmdrewrite.py |
| diffstat | 1 files changed, 4 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/hgext3rd/evolve/cmdrewrite.py Tue Aug 21 12:14:04 2018 +0200 +++ b/hgext3rd/evolve/cmdrewrite.py Tue Aug 21 12:13:28 2018 +0200 @@ -954,11 +954,10 @@ def cmdprune(ui, repo, *revs, **opts): """mark changesets as obsolete or succeeded by another changeset - Pruned changesets are obsolete with no successors. If they also have no - descendants, they are hidden (invisible to all commands). - - Non-obsolete descendants of pruned changesets become "unstable". Use :hg:`evolve` - to handle this situation. + Pruning changesets marks them obsolete, hiding them from the + history log, provided they have no descendants. Otherwise, all + such descendants that aren't themselves obsolete become + "unstable". Use :hg:`evolve` to handle this situation. When you prune the parent of your working copy, Mercurial updates the working copy to a non-obsolete parent.