touch: prompt the user for what to do with the revived changeset This patch improves our interface for reviving changesets. This patch makes touch not assume that the user wants to create divergence by default and gives a prompt instead. The prompt is skipped for changeset that have no living successor as no divergence would be created by reviving them anyway. To restore the previous behavior, one should now use the --allowdivergence flag. The prompt looks like: [10] <description> reviving this changeset will create divergence unless you make a duplicate. (a)llow divergence or (d)uplicate the changeset? a In further patches we will want to add one more choice to that prompt, for example having a marker between the old and revived nodes but no divergence displayed on the UI.

     1

recursive-include docs/figures *.svg

     2

include docs/figures/hgview-example.png

     3

include docs/*.rst

     4

include docs/*.py

     5

include docs/tutorials/*.t

     6

include docs/makefile

     7

include docs/static/*.svg

     8

include hgext/__init__.py

     9

include hgext/evolve.py

    10

include hgext/pushexperiment.py

    11

include hgext/simple4server.py

    12

include setup.py

    13

include README

    14

include COPYING

    15

include tests/*.t

    16

include tests/*.py

    17

include tests/_exc-util.sh

    18

include tests/dummyssh

    19

exclude tests/test-oldconvert.t

    20

exclude tests/test-qsync.t

    21

exclude tests/test-drop.t