view tests/test-manifest-merging.t @ 45711:3d68b47e461b

rewriteutil: handle dropped commits when updating description hashes

In looking to leverage this with the absorb extension, the old -> new mapping
there allows the new value to be None.  We could filter that out and not pass it
to this method, but it seems worth a message to the user.  (I wonder if these
should be an info or warning, because it's unlikely people are using `-v`
regularly.)

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

  $ hg init base

  $ cd base
  $ echo 'alpha' > alpha
  $ hg ci -A -m 'add alpha'
  adding alpha
  $ cd ..

  $ hg clone base work
  updating to branch default
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

  $ cd work
  $ echo 'beta' > beta
  $ hg ci -A -m 'add beta'
  adding beta
  $ cd ..

  $ cd base
  $ echo 'gamma' > gamma
  $ hg ci -A -m 'add gamma'
  adding gamma
  $ cd ..

  $ cd work
  $ hg pull -q
  $ hg merge
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
  (branch merge, don't forget to commit)

Update --clean to revision 1 to simulate a failed merge:

  $ rm alpha beta gamma
  $ hg update --clean 1
  2 files updated, 0 files merged, 0 files removed, 0 files unresolved

  $ cd ..