equal
deleted
inserted
replaced
3 ================================== |
3 ================================== |
4 Changeset Evolution with Mercurial |
4 Changeset Evolution with Mercurial |
5 ================================== |
5 ================================== |
6 |
6 |
7 `evolve`_ is a Mercurial extension for faster and safer mutable history. It |
7 `evolve`_ is a Mercurial extension for faster and safer mutable history. It |
8 implements the changeset evolution concept for `Mercurial`_. |
8 implements the `changeset evolution`_ concept for `Mercurial`_. |
9 |
9 |
10 * It offers a safe and simple way to refine changesets locally and propagate |
10 * It offers a safe and simple way to refine changesets locally and propagate |
11 those changes to other repositories. |
11 those changes to other repositories. |
12 |
12 |
13 * It can automatically detect and handle the complex issues that can arise from |
13 * It can automatically detect and handle the complex issues that can arise from |
52 index |
52 index |
53 user-guide |
53 user-guide |
54 sharing |
54 sharing |
55 concepts |
55 concepts |
56 from-mq |
56 from-mq |
|
57 |
|
58 .. _`changeset evolution`: |
57 |
59 |
58 What is Changeset Evolution ? |
60 What is Changeset Evolution ? |
59 ----------------------------- |
61 ----------------------------- |
60 |
62 |
61 With core Mercurial, changesets are permanent and immutable. You can |
63 With core Mercurial, changesets are permanent and immutable. You can |
120 edition, but at the changeset level. |
122 edition, but at the changeset level. |
121 |
123 |
122 Why the `evolve` extension |
124 Why the `evolve` extension |
123 -------------------------- |
125 -------------------------- |
124 |
126 |
125 Mercurial core already has some support for changeset evolution so why have a |
127 Mercurial core already has some support for `changeset evolution`_ so why have a |
126 dedicated extension? |
128 dedicated extension? |
127 |
129 |
128 The long-term plan for ``evolve`` is to add it to core Mercurial. However, |
130 The long-term plan for ``evolve`` is to add it to core Mercurial. However, |
129 having the extension helps us experimenting with various user experience |
131 having the extension helps us experimenting with various user experience |
130 approaches and technical prototype. Having a dedicated extensions help current |
132 approaches and technical prototype. Having a dedicated extensions help current |
135 relevant code go upstream. |
137 relevant code go upstream. |
136 |
138 |
137 Development status |
139 Development status |
138 ------------------ |
140 ------------------ |
139 |
141 |
140 While well on the way, the full implementation of the changeset evolution |
142 While well on the way, the full implementation of the `changeset evolution`_ |
141 concept is still in progress. Core Mercurial already supports many of the |
143 concept is still in progress. Core Mercurial already supports many of the |
142 associated features, but for now they are still disabled by default. The current |
144 associated features, but for now they are still disabled by default. The current |
143 implementation has been usable for multiple years already, and some parts of it |
145 implementation has been usable for multiple years already, and some parts of it |
144 are used in production in multiple projects and companies (including the |
146 are used in production in multiple projects and companies (including the |
145 Mercurial project itself, Facebook, Google, etc…). |
147 Mercurial project itself, Facebook, Google, etc…). |