##// END OF EJS Templates
upstream » mercurial-mirror
RSS

Clone from https://www.mercurial-scm.org/repo/hg-all

largefiles: update help...
Mads Kiilerich -
r18975:aa8205a9 default
parent child Browse files
Show More
Show file before | Show file after | Hide comments
@@ -41,24 +41,23 b' Note that the remote Mercurial must also'
41 enabled for this to work.
41 enabled for this to work.
42
42
43 When you pull a changeset that affects largefiles from a remote
43 When you pull a changeset that affects largefiles from a remote
44 repository, the largefiles for the changeset won't be pulled down.
44 repository, the largefiles for the changeset will by default not be
45 Instead, when you later update to such a revision, any largefiles
45 pulled down. However, when you update to such a revision, any
46 needed by that revision are downloaded and cached (if they have
46 largefiles needed by that revision are downloaded and cached (if
47 never been downloaded before). This means that network access may
47 they have never been downloaded before). One way to pull largefiles
48 be required to update to changesets you have previously updated to.
48 when pulling is thus to use --update, which will update your working
49 copy to the latest pulled revision (and thereby downloading any new
50 largefiles).
49
51
50 If you know you are pulling from a non-default location and want to
52 If you just want to ensure that you will have the largefiles needed to
51 ensure that you will have the largefiles needed to merge or rebase
53 merge or rebase with new heads that you are pulling, then you can pull
52 with new heads that you are pulling, then you can pull with the
54 with `--cache-largefiles` flag to pre-emptively download any largefiles
53 --cache-largefiles flag to pre-emptively download any largefiles
54 that are new in the heads you are pulling.
55 that are new in the heads you are pulling.
55
56
56 The one exception to the "largefiles won't be pulled until you update
57 Keep in mind that network access may now be required to update to
57 to a revision that changes them" rule is when you pull new heads.
58 changesets that you have not previously updated to. The nature of the
58 Because you could be pulling new heads (that you may later want to
59 largefiles extension means that updating is no longer guaranteed to
59 merge with) from a non-default location (that Mercurial won't know
60 be a local-only operation.
60 about later), when you pull new heads, largefiles revisions for those
61 heads are downloaded and cached locally.
62
61
63 If you already have large files tracked by Mercurial without the
62 If you already have large files tracked by Mercurial without the
64 largefiles extension, you will need to convert your repository in
63 largefiles extension, you will need to convert your repository in
General Comments 0
You need to be logged in to leave comments. Login now