Mercurial > evolve
changeset 2884:5a836fa589a4
doc-front-page: link to the changeset evolution section in the document
The section is unlikely to be perfect, but at least it exists.
| author | Pierre-Yves David <pierre-yves.david@octobus.net> |
|---|---|
| date | Wed, 30 Aug 2017 11:36:47 +0200 |
| parents | a23045b61e6d |
| children | e61a9fde2125 |
| files | docs/index.rst |
| diffstat | 1 files changed, 5 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/docs/index.rst Wed Aug 30 11:26:00 2017 +0200 +++ b/docs/index.rst Wed Aug 30 11:36:47 2017 +0200 @@ -5,7 +5,7 @@ ================================== `evolve`_ is a Mercurial extension for faster and safer mutable history. It -implements the changeset evolution concept for `Mercurial`_. +implements the `changeset evolution`_ concept for `Mercurial`_. * It offers a safe and simple way to refine changesets locally and propagate those changes to other repositories. @@ -55,6 +55,8 @@ concepts from-mq +.. _`changeset evolution`: + What is Changeset Evolution ? ----------------------------- @@ -122,7 +124,7 @@ Why the `evolve` extension -------------------------- -Mercurial core already has some support for changeset evolution so why have a +Mercurial core already has some support for `changeset evolution`_ so why have a dedicated extension? The long-term plan for ``evolve`` is to add it to core Mercurial. However, @@ -137,7 +139,7 @@ Development status ------------------ -While well on the way, the full implementation of the changeset evolution +While well on the way, the full implementation of the `changeset evolution`_ concept is still in progress. Core Mercurial already supports many of the associated features, but for now they are still disabled by default. The current implementation has been usable for multiple years already, and some parts of it