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 repo

     2

  $ cd repo

     3

  $ touch unknown

     4

     5

  $ touch a

     6

  $ hg add a

     7

  $ hg ci -m "1"

     8

     9

  $ touch b

    10

  $ hg add b

    11

  $ hg ci -m "2"

    12

    13

Should show unknown

    14

    15

  $ hg status

    16

  ? unknown

    17

  $ hg revert -r 0 --all

    18

  removing b

    19

    20

Should show unknown and b removed

    21

    22

  $ hg status

    23

  R b

    24

  ? unknown

    25

    26

Should show a and unknown

    27

    28

  $ ls -A

    29

  .hg

    30

  a

    31

  unknown