equal
deleted
inserted
replaced
1 What are phases? |
1 What are phases? |
2 ---------------- |
2 ================ |
3 |
3 |
4 Phases are a system for tracking which changesets have been or should |
4 Phases are a system for tracking which changesets have been or should |
5 be shared. This helps prevent common mistakes when modifying history |
5 be shared. This helps prevent common mistakes when modifying history |
6 (for instance, with the mq or rebase extensions). |
6 (for instance, with the mq or rebase extensions). |
7 |
7 |
15 can be in a lower phase than its ancestors. For instance, if a |
15 can be in a lower phase than its ancestors. For instance, if a |
16 changeset is public, all its ancestors are also public. Lastly, |
16 changeset is public, all its ancestors are also public. Lastly, |
17 changeset phases should only be changed towards the public phase. |
17 changeset phases should only be changed towards the public phase. |
18 |
18 |
19 How are phases managed? |
19 How are phases managed? |
20 ----------------------- |
20 ======================= |
21 |
21 |
22 For the most part, phases should work transparently. By default, a |
22 For the most part, phases should work transparently. By default, a |
23 changeset is created in the draft phase and is moved into the public |
23 changeset is created in the draft phase and is moved into the public |
24 phase when it is pushed to another repository. |
24 phase when it is pushed to another repository. |
25 |
25 |
27 refuse to operate on them to prevent creating duplicate changesets. |
27 refuse to operate on them to prevent creating duplicate changesets. |
28 Phases can also be manually manipulated with the :hg:`phase` command |
28 Phases can also be manually manipulated with the :hg:`phase` command |
29 if needed. See :hg:`help -v phase` for examples. |
29 if needed. See :hg:`help -v phase` for examples. |
30 |
30 |
31 Phases and servers |
31 Phases and servers |
32 ------------------ |
32 ================== |
33 |
33 |
34 Normally, all servers are ``publishing`` by default. This means:: |
34 Normally, all servers are ``publishing`` by default. This means:: |
35 |
35 |
36 - all draft changesets that are pulled or cloned appear in phase |
36 - all draft changesets that are pulled or cloned appear in phase |
37 public on the client |
37 public on the client |
57 .. note:: |
57 .. note:: |
58 Servers running older versions of Mercurial are treated as |
58 Servers running older versions of Mercurial are treated as |
59 publishing. |
59 publishing. |
60 |
60 |
61 Examples |
61 Examples |
62 -------- |
62 ======== |
63 |
63 |
64 - list changesets in draft or secret phase:: |
64 - list changesets in draft or secret phase:: |
65 |
65 |
66 hg log -r "not public()" |
66 hg log -r "not public()" |
67 |
67 |