hg-cpython: fallback when encountering an unknown matcher At this point in the process, nothing user-visible has happened, it is still safe to fallback. This can happen now that we're going to be using "container matchers" like unionmatcher and intersectionmatcher. This is easier and less error-prone than recursive checking beforehand since only the presence of a transformation case will allow the process to continue.

     1

Test issue2761

     2

     3

  $ hg init

     4

     5

  $ touch to-be-deleted

     6

  $ hg add

     7

  adding to-be-deleted

     8

  $ hg ci -m first

     9

  $ echo a > to-be-deleted

    10

  $ hg ci -m second

    11

  $ rm to-be-deleted

    12

  $ hg diff -r 0

    13

    14

Same issue, different code path

    15

    16

  $ hg up -C

    17

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

    18

  $ touch does-not-exist-in-1

    19

  $ hg add

    20

  adding does-not-exist-in-1

    21

  $ hg ci -m third

    22

  $ rm does-not-exist-in-1

    23

  $ hg diff -r 1