discovery: add extinct changesets to outgoing.excluded Before this change, push would incorrectly fast-path the bundle generation when extinct changesets are involved, because they are not added to outgoing.excluded. The reason to do so are related to outgoing.excluded being assumed to contain only secret changesets by scmutil.nochangesfound(), when displaying warnings like: changes found (ignored 9 secret changesets) Still, outgoing.excluded seems like a good API to report the extinct changesets instead of dedicated code and nothing in the docstring indicates it to be bound to secret changesets. This patch adds extinct changesets to outgoing.excluded and fixes scmutil.nochangesfound() to filter the excluded node list. Original version and test by Pierre-Yves.David@ens-lyon.org

     1

  $ "$TESTDIR/hghave" execbit || exit 80

     2

     3

  $ hg init

     4

  $ echo a > a

     5

  $ hg ci -Am'not executable'

     6

  adding a

     7

     8

  $ chmod +x a

     9

  $ hg ci -m'executable'

    10

  $ hg id

    11

  79abf14474dc tip

    12

    13

Make sure we notice the change of mode if the cached size == -1:

    14

    15

  $ hg rm a

    16

  $ hg revert -r 0 a

    17

  $ hg debugstate

    18

  n   0         -1 unset               a

    19

  $ hg status

    20

  M a

    21

    22

  $ hg up 0

    23

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

    24

  $ hg id

    25

  d69afc33ff8a

    26

  $ test -x a && echo executable -- bad || echo not executable -- good

    27

  not executable -- good

    28