view tests/test-evolve-content-divergent-first-changeset.t @ 6317:53d63b608230

evolve: stop preserving all of {extras} for uninterrupted evolve operations I doubt the wisdom of doing this, but the case of completing interrupted evolves does this, as do core commands for amend, graft, and rebase in hg ce9696193175, bb14a81ce647, and b698abf971e7. Note the obslog order (and DAG display) change in test-evolve-content-divergent-relocation.t around line 131. I have no idea why that would happen, or if it's an indicator of something subtle going on.
author Matt Harbison <matt_harbison@yahoo.com>
date Fri, 07 Oct 2022 20:32:14 -0400
parents 83ceafbaa7d6
children 88f9bbba392d
line wrap: on
line source

  $ . $TESTDIR/testlib/pythonpath.sh
  $ cat >> $HGRCPATH << EOF
  > [extensions]
  > evolve=
  > [experimental]
  > evolution.allowdivergence = True
  > EOF

This test file tests the case of content-divergence resolution of changesets
that have the null revision as the parent.

  $ hg init issue6201
  $ cd issue6201

  $ touch test
  $ hg add test
  $ hg commit -m test
  $ hg log -T '{node|short}\n'
  be090ea66256

  $ echo a >> test
  $ hg amend -m div1
  $ hg log -T '{node|short}\n'
  79fa0eb22d65

  $ hg up be090ea66256 --hidden --quiet
  updated to hidden changeset be090ea66256
  (hidden revision 'be090ea66256' was rewritten as: 79fa0eb22d65)
  working directory parent is obsolete! (be090ea66256)
  $ echo a >> test
  $ echo b >> test
  $ hg amend -m div2
  2 new content-divergent changesets
  $ hg log -T '{node|short}\n'
  4b2524b7508e
  79fa0eb22d65

  $ hg evolve --content-divergent --tool :other
  merge:[1] div1
  with: [2] div2
  base: [0] test
  0 files updated, 1 files merged, 0 files removed, 0 files unresolved
  working directory is now at 62fcb3488421

  $ hg evolve --list