Mercurial > evolve
comparison docs/evolve-faq.rst @ 492:7ecd41520dae
rename `stabilize` to `evolve`
stabilize keep being valide but as Matt still like "Changeset Evolution" as a
name evolve make more sense.
Stabilize is a bit too tight to unstable too.
author | Pierre-Yves David <pierre-yves.david@logilab.fr> |
---|---|
date | Fri, 24 Aug 2012 11:17:18 +0200 |
parents | d702f0d26c6a |
children | 4387e62bd4f4 |
comparison
equal
deleted
inserted
replaced
491:6989d8fe4ed2 | 492:7ecd41520dae |
---|---|
150 You can still use rebase to move a whole segment of the changeset graph together. | 150 You can still use rebase to move a whole segment of the changeset graph together. |
151 | 151 |
152 .. warning:: Beware that rebasing obsolete changesets will result in | 152 .. warning:: Beware that rebasing obsolete changesets will result in |
153 conflicting versions of the changesets. | 153 conflicting versions of the changesets. |
154 | 154 |
155 Stabilize history: ``stabilize`` | 155 Stabilize history: ``evolve`` |
156 ------------------------------------------------------------ | 156 ------------------------------------------------------------ |
157 | 157 |
158 When you rewrite (amend) a changeset with children without rewriting | 158 When you rewrite (amend) a changeset with children without rewriting |
159 those children you create *unstable* changesets and *suspended | 159 those children you create *unstable* changesets and *suspended |
160 obsolete* changesets. | 160 obsolete* changesets. |
162 When you are finished amending a given changeset, you will want to | 162 When you are finished amending a given changeset, you will want to |
163 declare it stable, in other words rebase its former descendants on its | 163 declare it stable, in other words rebase its former descendants on its |
164 newest version. This is not done automatically to avoid the | 164 newest version. This is not done automatically to avoid the |
165 proliferation of useless hidden changesets. | 165 proliferation of useless hidden changesets. |
166 | 166 |
167 .. warning:: ``hg stabilize`` have no --continue to use after conflict | |
168 resolution | |
169 | |
170 .. warning:: stabilization does not handle deletion yet. | |
171 | |
172 .. warning:: obsolete currently relies on changesets in secret phase | |
173 to avoid exchanging obsolete and unstable changesets. | |
174 | |
175 XXX details issue here | |
176 | |
177 | 167 |
178 Fix my history afterward: ``prune -n`` | 168 Fix my history afterward: ``prune -n`` |
179 ------------------------------------------------------------ | 169 ------------------------------------------------------------ |
180 | 170 |
181 Sometimes you need to create an obsolete marker by hand. This may happen when | 171 Sometimes you need to create an obsolete marker by hand. This may happen when |