$ cat >> $HGRCPATH <<EOF

  > [ui]

  > logtemplate={rev}:{node|short} {desc}\n

  > [defaults]

  > amend=-d "0 0"

  > [extensions]

  > hgext.rebase=

  > EOF

  $ echo "evolve=$(echo $(dirname $TESTDIR))/hgext3rd/evolve/" >> $HGRCPATH

  $ hg init repo

  $ cd repo

  $ echo A > a

  $ hg add a

  $ hg commit -m a

Basic usage

  $ hg log -G

  @  0:[0-9a-f]{12} a (re)

  $ hg touch .

  $ hg log -G

  @  1:[0-9a-f]{12} a (re)

Revive usage

  $ echo A > b

  $ hg add b

  $ hg commit -m ab --amend

  $ hg up --hidden 1

  0 files updated, 0 files merged, 1 files removed, 0 files unresolved

  working directory parent is obsolete! (*) (glob)

  (use 'hg evolve' to update to its successor: *) (glob)

  $ hg log -G

  @  1:[0-9a-f]{12} a (re)

  $ hg touch .

  [1] a

  reviving this changeset will create divergence unless you make a duplicate.

  (a)llow divergence or (d)uplicate the changeset?  a

  $ hg log -G

  0 files updated, 0 files merged, 1 files removed, 0 files unresolved

  working directory now at 000000000000

  1 changesets pruned

Duplicate

  $ hg touch --duplicate .

  $ hg log -G

Multiple touch

  $ echo C > c

  $ hg add c

  $ hg commit -m c

  $ echo D > d

  $ hg add d

  $ hg commit -m d

  $ hg log -G

  |

  |

  $ hg touch .^:.

  $ hg log -G

  |

  |

check move data kept after rebase on touch:

  $ touch gna1

  $ hg commit -Am gna1

  adding gna1

  $ hg mv gna1 gna2

  $ hg commit -m move

  $ hg st -C --change=tip

  A gna2

    gna1

  R gna1

  $ hg up .^

  1 files updated, 0 files merged, 1 files removed, 0 files unresolved

  $ hg touch

  $ hg log -G --hidden

  |

  | x  9:[0-9a-f]{12} gna1 (re)

  |/

  |

  |

  | |

  |/

  x  1:[0-9a-f]{12} a (re)

  x  0:[0-9a-f]{12} a (re)

  $ hg st -C --change=tip

  A gna2

    gna1

  R gna1

check that the --duplicate option does not create divergence

check that reviving a changeset with no successor does not show the prompt

  1 changesets pruned