Size: 1023
Comment:
|
Size: 1195
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 11: | Line 11: |
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. |
changesets exchanged ([[#Available_Phases|read more]]). This phase concept aims to "just works" in a transparent manner for any user ([[#Phase_Movements|read more]]). It is part of Core and always enabled in any new client but doesn't prevent older client to work on a repository ([[#Upgrade_Notes|read more]]). Advanced user may decide handle phase manually ([[#Publishing Repository|read more]]). |
Line 18: | Line 19: |
== Available phase == | == Available Phases == |
Line 20: | Line 21: |
* Prevent accidental rewritting part of the history expected to be immutable. * Keep immature changeset to be exchanged by mistake. |
* Prevent accidental rewritting part of the history expected to be immutable. * Keep immature changeset to be exchanged by mistake. |
Line 30: | Line 31: |
[[Phases#core_command|coin]] | |
Line 31: | Line 33: |
== Phase movement == |
== Phase Movements == |
Line 41: | Line 42: |
== Publishing repository == | == Publishing Repository == |
Line 43: | Line 44: |
== upgrade notes == | == Upgrade Notes == |
Phases
Contents
1. Introduction
The phase concept improves safety of history rewriting and control over changesets exchanged (read more). This phase concept aims to "just works" in a transparent manner for any user (read more). It is part of Core and always enabled in any new client but doesn't prevent older client to work on a repository (read more). Advanced user may decide handle phase manually (read more).
This concept is introduced in Mercurial 2.1.
2. Available Phases
- 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 Movements
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)