bisect: avoid copying ancestor list for non-merge commits During a bisection, hg needs to compute a list of all ancestors for every candidate commit. This is accomplished via a bottom-up traversal of the set of candidates, during which each revision's ancestor list is populated using the ancestor list of its parent(s). Previously, this involved copying the entire list, which could be very long in if the bisection range was large. To help improve this, we can observe that each candidate commit is visited exactly once, at which point its ancestor list is copied into its children's lists and then dropped. In the case of non-merge commits, a commit's ancestor list consists exactly of its parent's list plus itself. This means that we can trivially reuse the parent's existing list for one of its non-merge children, which avoids copying entirely if that commit is the parent's only child. This makes bisections over linear ranges of commits much faster. During some informal testing in the large publicly-available `mozilla-central` repository, this noticeably sped up bisections over large ranges of history: Setup: $ cd mozilla-central $ hg bisect --reset $ hg bisect --good 0 $ hg log -r tip -T '{rev}\n' 628417 Test: $ time hg bisect --bad tip --noupdate Before: real 3m35.927s user 3m35.553s sys 0m0.319s After: real 1m41.142s user 1m40.810s sys 0m0.285s

     1

#require symlink

     2

     3

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

     4

     5

  $ hg init

     6

     7

  $ ln -s foo link

     8

  $ hg add link

     9

  $ hg ci -mbad link

    10

  $ hg rm link

    11

  $ hg ci -mok

    12

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

    13

    14

  $ hg up 0

    15

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

    16

    17

  $ hg import --no-commit bad.patch

    18

  applying bad.patch

    19

    20

  $ hg status

    21

  R link

    22

  ? bad.patch

    23