stabilize: improve unstable selection heuristic Without argument, stabilize was picking the first in: "unstable() and ((suspended() or obsancestors(::.))::)" which usually returned the "oldest" unstable revision in parent predecessors descendants. This revision is interesting because it usually gives "soft" merges but rebasing it left the working directory on a remote branch, which was very confusing. The new heuristic picks an unstable changeset which can be rebased on top of the parent revision, or on top of one of its descendants (selected in revision order). This has the advantage of selecting a revision which can be rebased on the current subtree, and leave the working directory in a more convenient location.

     1

=============================

     2

Mutable History For Mercurial

     3

=============================

     4

     5

:obsolete:

     6

     7

    Introduce an ``obsolete`` concept that tracks new versions of rewritten

     8

    changesets.

     9

    10

:evolve:

    11

    A collection of commands to rewrite the mutable part of the history.

    12

    13

    14

    15

**These extensions are experimental and are not meant for production.**

    16

    17

    18

See doc/ directory for details

    19

    20

Contribute

    21

==================

    22

    23

The simplest way to contribute is to issue a pull request on bitbucket.

    24

    25

However, some cutting edge change may be found in a mutable repository hosted

    26

by logilab before they are published.

    27

    28

    http://hg-lab.logilab.org/wip/mutable-history/

    29

    30

Make sure to check lastest draft changeset before submitting new changeset.

    31

    32