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 a

     2

  $ cd a

     3

  $ echo 123 > a

     4

  $ hg add a

     5

  $ hg commit -m "a" -u a

     6

     7

  $ cd ..

     8

  $ hg init b

     9

  $ cd b

    10

  $ echo 321 > b

    11

  $ hg add b

    12

  $ hg commit -m "b" -u b

    13

    14

  $ hg pull ../a

    15

  pulling from ../a

    16

  searching for changes

    17

  abort: repository is unrelated

    18

  [255]

    19

    20

  $ hg pull -f ../a

    21

  pulling from ../a

    22

  searching for changes

    23

  warning: repository is unrelated

    24

  requesting all changes

    25

  adding changesets

    26

  adding manifests

    27

  adding file changes

    28

  added 1 changesets with 1 changes to 1 files (+1 heads)

    29

  new changesets 9a79c33a9db3

    30

  (run 'hg heads' to see heads, 'hg merge' to merge)

    31

    32

  $ hg heads

    33

  changeset:   1:9a79c33a9db3

    34

  tag:         tip

    35

  parent:      -1:000000000000

    36

  user:        a

    37

  date:        Thu Jan 01 00:00:00 1970 +0000

    38

  summary:     a

    39

    40

  changeset:   0:01f8062b2de5

    41

  user:        b

    42

  date:        Thu Jan 01 00:00:00 1970 +0000

    43

  summary:     b

    44

    45

    46

  $ cd ..