phases: use revision number in new_heads All graph operations will be done using revision numbers, so passing nodes only means they will eventually get converted to revision numbers internally. As part of an effort to align the code on using revision number we make the `phases.newheads` function operated on revision number, taking them as input and using them in returns, instead of the node-id it used to consume and produce. This is part of multiple changesets effort to translate more part of the logic, but is done step by step to facilitate the identification of issue that might arise in mercurial core and extensions. To make the change simpler to handle for third party extensions, we also rename the function, using a more modern form. This will help detecting the different between the node-id version and the rev-num version. I also take this as an opportunity to add some comment about possible performance improvement for the future. They don't matter too much now, but they are worse exploring in a while.

     1

  $ hg init r1

     2

  $ cd r1

     3

  $ hg ci --config ui.allowemptycommit=true -m c0

     4

  $ hg ci --config ui.allowemptycommit=true -m c1

     5

  $ hg ci --config ui.allowemptycommit=true -m c2

     6

  $ hg co -q 0

     7

  $ hg ci --config ui.allowemptycommit=true -m c3

     8

  created new head

     9

  $ hg co -q 3

    10

  $ hg merge --quiet

    11

  $ hg ci --config ui.allowemptycommit=true -m c4

    12

    13

  $ hg log -G -T'{desc}'

    14

  @    c4

    15

  |\

    16

  | o  c3

    17

  | |

    18

  o |  c2

    19

  | |

    20

  o |  c1

    21

  |/

    22

  o  c0

    23

    24

    25

  >>> from mercurial import hg

    26

  >>> from mercurial import ui as uimod

    27

  >>> repo = hg.repository(uimod.ui())

    28

  >>> for anc in repo.changelog.ancestors([4], inclusive=True):

    29

  ...   print(anc)

    30

  4

    31

  3

    32

  2

    33

  1

    34

  0