Mercurial > evolve

comparison tests/test-evolve.t @ 1585:6cdc0dee9d58

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
tests: fix change to help output Core have made minor update to its documentation.
author Pierre-Yves David <pierre-yves.david@fb.com>
date Sun, 17 Jan 2016 21:09:45 -0800
parents c4f8a2916e43
children ea7523380efa dcf145d0ce21
comparison
equal deleted inserted replaced
1583:aaa65373a31b 1585:6cdc0dee9d58
53 Unlike the previous way of handling such changes, by stripping the old 53 Unlike the previous way of handling such changes, by stripping the old
54 changesets from the repository, obsolescence markers can be propagated 54 changesets from the repository, obsolescence markers can be propagated
55 between repositories. This allows for a safe and simple way of exchanging 55 between repositories. This allows for a safe and simple way of exchanging
56 mutable history and altering it after the fact. Changeset phases are 56 mutable history and altering it after the fact. Changeset phases are
57 respected, such that only draft and secret changesets can be altered (see 57 respected, such that only draft and secret changesets can be altered (see
58 "hg hg phases" for details). 58 'hg hg phases' for details).
59 59
60 Obsolescence is tracked using "obsolete markers", a piece of metadata 60 Obsolescence is tracked using "obsolete markers", a piece of metadata
61 tracking which changesets have been made obsolete, potential successors 61 tracking which changesets have been made obsolete, potential successors
62 for a given changeset, the moment the changeset was marked as obsolete, 62 for a given changeset, the moment the changeset was marked as obsolete,
63 and the user who performed the rewriting operation. The markers are stored 63 and the user who performed the rewriting operation. The markers are stored