phases: avoid N² behavior in `advanceboundary` We allowed duplicated entries in the deque, which each entry could potentially insert all its ancestors. So advancing boundary for the full repository would mean each revision would walk all its ancestors, resulting in O(N²) iteration. For repository of any decent size, N² is quickly insane. We introduce a simple set to avoid this and get back to reasonable performance.

     1

  $ hg init

     2

     3

  $ echo 123 > a

     4

  $ hg add a

     5

  $ hg commit -m "first" a

     6

     7

  $ mkdir sub

     8

  $ echo 321 > sub/b

     9

  $ hg add sub/b

    10

  $ hg commit -m "second" sub/b

    11

    12

  $ cat sub/b

    13

  321

    14

    15

  $ hg co 0

    16

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

    17

    18

  $ cat sub/b 2>/dev/null || echo "sub/b not present"

    19

  sub/b not present

    20

    21

  $ test -d sub || echo "sub not present"

    22

  sub not present

    23