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

#require symlink

     2

     3

https://bz.mercurial-scm.org/1438

     4

     5

  $ hg init repo

     6

  $ cd repo

     7

     8

  $ ln -s foo link

     9

  $ hg add link

    10

  $ hg ci -mbad link

    11

  $ hg rm link

    12

  $ hg ci -mok

    13

  $ hg diff -g -r 0:1 > bad.patch

    14

    15

  $ hg up 0

    16

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

    17

    18

  $ hg import --no-commit bad.patch

    19

  applying bad.patch

    20

    21

  $ hg status

    22

  R link

    23

  ? bad.patch

    24