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

Issue1678: IndexError when pushing

     2

     3

setting up base repo

     4

  $ hg init a

     5

  $ cd a

     6

  $ touch a

     7

  $ hg ci -Am a

     8

  adding a

     9

  $ cd ..

    10

    11

cloning base repo

    12

  $ hg clone a b

    13

  updating to branch default

    14

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

    15

  $ cd b

    16

    17

setting up cset to push

    18

  $ hg up null

    19

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

    20

  $ touch a

    21

different msg so we get a clog new entry

    22

  $ hg ci -Am b

    23

  adding a

    24

  created new head

    25

    26

pushing

    27

  $ hg push -f ../a

    28

  pushing to ../a

    29

  searching for changes

    30

  adding changesets

    31

  adding manifests

    32

  adding file changes

    33

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

    34

    35

  $ cd ..