match: compose 'set:' pattern as matcher Baby step towards porting fileset to matcher composition. We can't use the exactmatcher since it would provide a computed set as exact paths. That's why we use the predicatematcher with fset.__contains__. This will be cleaned up later. The test change in test-glog.t means that the "set:copied()" pattern is no longer be processed as a slow path. That's because the fset is empty. This will also change in future patches.

     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