Mercurial > evolve

comparison hgext/evolve.py @ 1709:989ed2f30d41 stable

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
help: fix evolution hg phases reference
author timeless@gmail.com
date Wed, 25 May 2016 19:13:26 +0000
parents b21ce82e6f76
children aec233d3cafd
comparison
equal deleted inserted replaced
1703:3460887b6859 1709:989ed2f30d41
31 Unlike the previous way of handling such changes, by stripping the old 31 Unlike the previous way of handling such changes, by stripping the old
32 changesets from the repository, obsolescence markers can be propagated 32 changesets from the repository, obsolescence markers can be propagated
33 between repositories. This allows for a safe and simple way of exchanging 33 between repositories. This allows for a safe and simple way of exchanging
34 mutable history and altering it after the fact. Changeset phases are 34 mutable history and altering it after the fact. Changeset phases are
35 respected, such that only draft and secret changesets can be altered (see 35 respected, such that only draft and secret changesets can be altered (see
36 :hg:`hg phases` for details). 36 :hg:`help phases` for details).
37 37
38 Obsolescence is tracked using "obsolete markers", a piece of metadata 38 Obsolescence is tracked using "obsolete markers", a piece of metadata
39 tracking which changesets have been made obsolete, potential successors for 39 tracking which changesets have been made obsolete, potential successors for
40 a given changeset, the moment the changeset was marked as obsolete, and the 40 a given changeset, the moment the changeset was marked as obsolete, and the
41 user who performed the rewriting operation. The markers are stored 41 user who performed the rewriting operation. The markers are stored