Mercurial changeset evolution and topic extension
branching: merge with stable
evolve: move status msg to verbose mode in content-divergence resolution
b78707559f1f — Anton Shestakov 1 year, 3 months ago
changelog: --no-update is the default, recommend --update instead


Mutable History For Mercurial

Evolve Extension

This package supplies the ``evolve`` extension for Mercurial,

**The full implementation of the changeset evolution concept is still in
progress.**  Please subscribe to the `evolve-testers mailing list
<>`_ to stay up to
date with changes.

This extension:

* enables the “changeset evolution” feature of Mercurial core,

* provides a set of commands to mutate your history,

* issues several warning messages when troubles from some mutable appears in
  your repository,

* provides an ``hg evolve`` command to deal with such "troubles",

* improves performance of obsolescence marker exchanges and discovery during
  push and pull.


We recommend reading the documentation first. An online version is
available here:

How to Install

Using Pip

You can install the latest evolution version usin pip::

    $ pip install --user hg-evolve

Then just enable it in you hgrc::

    $ hg config --edit # adds the two line below:
    evolve =

From Source

To install a local version from source::

    $ hg clone
    $ cd evolve
    $ pip install --user .

Then just enable it in you hgrc::

    $ hg config --edit # adds the two line below:
    evolve =

Documentation lives in ``doc/``.

Server Only Setup

It is possible to enable a smaller subset of the extensions aimed at server
serving repository. It skips the additions of the new commands and local UI
messages that might add performance overheads. To use the server only
extension, install the package and use::

    $ hg config --edit # adds the two line below:
    evolve.serveronly =

Extension Purpose

The goal of this extension is to provide an appropriate place for code and
concept related to changeset evolution to mature. In this extension we allow
for hackier code, unlocking quick experimentation and faster iterations.

In addition, the evolve extensions support a wider set of Mercurial version,
allowing us to reach a larger user base for feedback. The Evolve extension is
not tight to the Mercurial release cycle and can release new feature and bug
fix at a higher rate if necessary.

Once a concept is ready enough, its implementation is moved into Mercurial
core. The maturation period helped us to get a clearer picture of what was
needed. During the upstreaming process, we can use this clearer picture to
clean up the code and upgrade it to an appropriate quality for Mercurial core.

How to Contribute

Discussion happens on the #hg-evolve IRC on freenode_.

.. _freenode:

Bugs are to be reported on the mercurial's bug tracker (component: `evolution`_):

.. _evolution:

You can use the patchbomb extension to send email to `mercurial devel
<>`_. Please make
sure to use the evolve-ext flag when doing so. You can use a command like

    $ hg email --to --flag evolve-ext --rev '<your patches>'

Some of development happens on a public bitbucket repository (`evolve-devel`_) using the topic extension.

.. _`evolve-devel`:

For guidelines on the patch description, see the `official Mercurial guideline`_.

.. _`official Mercurial guideline`:

Please don't forget to update and run the tests when you fix a bug or
add a feature. To run the tests, you need a working copy of Mercurial,
say in $HGSRC::

    $ cd tests
    $ python $HGSRC/tests/

Branch policy

The evolve test are highly impacted by changes in core. To deal with this, we use named branches.

There are two main branches: "stable" and "default". Tests on these branch are
supposed to pass with the corresponding "default" and "stable" branch from core
Mercurial. The documentation is built from the tip of stable.

In addition, we have compatibility branches to check tests on older version of
Mercurial. They are the "mercurial-x.y" branches. They are used to apply
expected test change only, no code change should happen there.

test output change from a changeset in core should adds the following line to their description: