evovle: remove redundancy in evolve output Copying the discription of this redundancy issue given by Pierre Yves David: When running `hg evolve` to stabilize orphan changeset output about the currently stabilized changeset is issued. For example: $ hg evolve move:[3] a3 atop:[4] a2 working directory is now at 7c5649f73d11 This output can become quite repetitive when orphan are stabilized atop each other. For example: $ hg evolve --all move:[8] dansk 2! atop:[10] dansk! merging main-file-1 move:[9] dansk 3! atop:[11] dansk 2! In this case it would be smoother to issue: $ hg evolve --all move:[8] dansk 2! atop:[10] dansk! merging main-file-1 move:[9] dansk 3! Since we are moving "dansk 3!" atop the changeset we just stabilized. When adding this be careful that we still want to issue the "atop" message in various cases: 1. first changesets in a stack 2. when the orphan is not stabilized atop previous one 3. when using hg evolve --continue to resume an evolution So, I have made the changes which also respect above listed three points. And changes in tests/test-evovle*.t reflecting the changed behavior.

     1

.. Copyright © 2017 Pierre-Yves David <pierre-yves.david@octobus.net>

     2

     3

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

     4

Known limitations of the current documentation

     5

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

     6

     7

Features not covered by tutorials

     8

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

     9

    10

Some of the *newer* features of evolution might not be reflected in the

    11

documentation yet. You can directly check the inline documentation of the

    12

extension itself for fresher details using `hg help -e evolve`.

    13

    14

Known undocumented features are:

    15

    16

 * `hg prev`,

    17

 * `hg next`,

    18

 * `hg next --evolve`,

    19

 * `hg evolve --rev`,

    20

 * `hg evolve --list`,

    21

 * `hg obslog`,

    22

 * `hg split`,

    23

 * `hg metaedit`,

    24

 * `hg touch`,

    25

 * `hg amend --extract`,

    26

 * `hg pdiff`,

    27

 * `hg pstatus`,

    28

 * `hg amend -i`,

    29

 * various topic related elements (in particular `hg stack`),

    30

    31

Unreferenced Documents

    32

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

    33

    34

There are documents with content not linked in the flow of the main

    35

documentation. Some might be outdated and some are too fresh to be integrated in

    36

the main flow yet.

    37

    38

.. toctree::

    39

   :maxdepth: 1

    40

    41

   evolve-faq

    42

   evolve-good-practice

    43

   obs-terms

    44

   tutorials/topic-tutorial

    45

   tutorials/tutorial