largefiles: use 'default' instead of 'default-push' when pulling (issue3584) This only applies to downloading largefiles, and only when no source for the pull is explicitly provided. The repository itself was properly being pulled via 'default' previously. Using --all-largefiles is not necessary on a bare pull to test this (this existing test is merely a convenience), but it is required to test pulling on the rebase path. Note that the errors generated in the --rebase case are because the repo specified doesn't have the largefiles in its cache (though they are in the user cache), so the errors are misleading. Specifying --all-largefiles when cloning to 'b' fixes this, but instead of errors, it reports caching only 5 largefiles instead of the 9 that come up missing. Likely this is because the largefile download procedure tries to download missing files for each rev, and some of the files have standins in more than one rev that gets pulled.

     1

  $ hg init repo

     2

  $ cd repo

     3

     4

  $ touch foo

     5

  $ hg ci -Am 'add foo'

     6

  adding foo

     7

     8

  $ hg up -C null

     9

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

    10

    11

this should be stored as a delta against rev 0

    12

    13

  $ echo foo bar baz > foo

    14

  $ hg ci -Am 'add foo again'

    15

  adding foo

    16

  created new head

    17

    18

  $ hg debugindex foo

    19

     rev    offset  length  ..... linkrev nodeid       p1           p2 (re)

    20

       0         0       0  .....       0 b80de5d13875 000000000000 000000000000 (re)

    21

       1         0      24  .....       1 0376abec49b8 000000000000 000000000000 (re)

    22

    23

  $ cd ..