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 |