comparison tests/test-absorb.t @ 42266:b3fc78c028ef

absorb: be more specific when erroring out on merge commit

When you have a merge commit checked out and run `hg absorb`, it would
tell you

  abort: no mutable changeset to change

That makes it sound like the problem is public commits when isn't
really. Let's be more specific in this case.

There was already a test case that test this, so that now prints the
new message. I added a new test case that shows the old message (when
a public commit is checked out).

Differential Revision: https://phab.mercurial-scm.org/D6354

42265:65f3a77223e0

  $ hg bookmarks
     b1                        1:a4183e9b3d31
     b2                        2:c9b20c925790
   * ba                        2:c9b20c925790

Non-mofified files are ignored:

  $ touch b
  $ hg commit -A b -m b
  $ touch c
  $ hg add c

  1: Insert before 2b
  1: 2b
  2: 4d
  2: insert aftert 4d

Make working copy clean:

  $ hg revert -q -C a b
  $ hg forget c
  $ rm c
  $ hg status

Merge commit will not be changed:

  o  0 commit 1 public
  
  $ echo 2 >> m1
  $ echo 2 >> m2
  $ hg absorb --apply-changes
  abort: no mutable changeset to change
  [255]
  $ hg revert -q -C m1 m2

Use a new repo:

42266:b3fc78c028ef

  $ hg bookmarks
     b1                        1:a4183e9b3d31
     b2                        2:c9b20c925790
   * ba                        2:c9b20c925790

Non-modified files are ignored:

  $ touch b
  $ hg commit -A b -m b
  $ touch c
  $ hg add c

  1: Insert before 2b
  1: 2b
  2: 4d
  2: insert aftert 4d

  $ hg co -qC 1
  $ sedi 's/Insert/insert/' a
  $ hg absorb --apply-changes
  abort: no mutable changeset to change
  [255]

Make working copy clean:

  $ hg co -qC ba
  $ rm c
  $ hg status

Merge commit will not be changed:

  o  0 commit 1 public
  
  $ echo 2 >> m1
  $ echo 2 >> m2
  $ hg absorb --apply-changes
  abort: cannot absorb into a merge
  [255]
  $ hg revert -q -C m1 m2

Use a new repo: