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

http://mercurial.selenic.com/bts/issue842

     2

     3

  $ hg init

     4

  $ echo foo > a

     5

  $ hg ci -Ama

     6

  adding a

     7

     8

  $ hg up -r0000

     9

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

    10

    11

  $ echo bar > a

    12

    13

Should issue new head warning:

    14

    15

  $ hg ci -Amb

    16

  adding a

    17

  created new head

    18

    19

  $ hg up -r0000

    20

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

    21

    22

  $ echo stuffy > a

    23

    24

Should not issue new head warning:

    25

    26

  $ hg ci -q -Amc

    27

    28

  $ hg up -r0000

    29

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

    30

    31

  $ echo crap > a

    32

  $ hg branch testing

    33

  marked working directory as branch testing

    34

  (branches are permanent and global, did you want a bookmark?)

    35

    36

Should not issue warning:

    37

    38

  $ hg ci -q -Amd

    39