hgext/largefiles/__init__.py
changeset 18704 d69585a5c5c0
parent 18599 5cd1dbf4c5d2
child 18975 aa8205a9f51a
equal deleted inserted replaced
18700:4a85ebb5c807 18704:d69585a5c5c0
    39 repository, its largefile revisions will be uploaded along with it.
    39 repository, its largefile revisions will be uploaded along with it.
    40 Note that the remote Mercurial must also have the largefiles extension
    40 Note that the remote Mercurial must also have the largefiles extension
    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 usually won't be
    44 repository, the largefiles for the changeset won't be pulled down.
    45 pulled down until you update to the revision (there is one exception
    45 Instead, when you later update to such a revision, any largefiles
    46 to this case).  However, when you update to such a revision, any
    46 needed by that revision are downloaded and cached (if they have
    47 largefiles needed by that revision are downloaded and cached (if
    47 never been downloaded before).  This means that network access may
    48 they have never been downloaded before).  This means that network
    48 be required to update to changesets you have previously updated to.
    49 access may be required to update to changesets you have no
    49 
    50 previously updated to.
    50 If you know you are pulling from a non-default location and want to
       
    51 ensure that you will have the largefiles needed to merge or rebase
       
    52 with new heads that you are pulling, then you can pull with the
       
    53 --cache-largefiles flag to pre-emptively download any largefiles
       
    54 that are new in the heads you are pulling.
    51 
    55 
    52 The one exception to the "largefiles won't be pulled until you update
    56 The one exception to the "largefiles won't be pulled until you update
    53 to a revision that changes them" rule is when you pull new heads.
    57 to a revision that changes them" rule is when you pull new heads.
    54 Because you could be pulling new heads (that you may later want to
    58 Because you could be pulling new heads (that you may later want to
    55 merge with) from a non-default location (that Mercurial won't know
    59 merge with) from a non-default location (that Mercurial won't know