Phases
Contents
1. Introduction
The phase concept improves safety of history rewriting and control over changesets exchanged. This phase concept aims to "just works" in a transparent manner for any user. It is part of Core and always enabled in any new client but doesn't prevent older client to work on a repository. Advanced user may decide handle phase manually.
This concept is introduced in Mercurial 2.1.
2. Available phase
* Prevent accidental rewritting part of the history expected to be immutable. * Keep immature changeset to be exchanged by mistake.
These phases share a hierarchy of traits:
|
immutable |
shared |
public |
x |
x |
draft |
|
x |
secret |
|
|
3. Phase movement
4. command line interface
4.1. core command
4.2. impact on extension
5. Publishing repository
6. upgrade notes
(If you were looking to the developer oriented page: PhaseDevel)