Document usage of git fetch --all with ref list
This commit is contained in:
parent
a817f35588
commit
6cd177d974
@ -25,10 +25,11 @@ This does not update the working copy.
|
||||
that would otherwise be downloaded. See [RECENT CHANGES]
|
||||
|
||||
* `--all`:
|
||||
Download all objects referenced by any commit that is reachable; this is
|
||||
primarily for backup / migration purposes. Cannot be combined with --recent or
|
||||
--include/--exclude. Ignores any globally configured include and exclude paths
|
||||
to ensure that all objects are downloaded.
|
||||
Download all objects that are referenced by any commit reachable from the refs
|
||||
provided as arguments. If no refs are provided, then all refs are pushed. This
|
||||
is primarily for backup and migration purposes. Cannot be combined with
|
||||
--recent or --include/--exclude. Ignores any globally configured include and
|
||||
exclude paths to ensure that all objects are downloaded.
|
||||
|
||||
* `--prune` `-p`:
|
||||
Prune old and unreferenced objects after fetching, equivalent to running
|
||||
@ -126,6 +127,11 @@ What changes are considered 'recent' is based on a number of gitconfig options:
|
||||
|
||||
`git lfs fetch upstream`
|
||||
|
||||
* Fetch all the LFS objects from the default remote that are referenced by any
|
||||
commit in the `master` and `develop` branches
|
||||
|
||||
`git lfs fetch --all master develop`
|
||||
|
||||
* Fetch the LFS objects for a branch from origin
|
||||
|
||||
`git lfs fetch origin mybranch`
|
||||
|
Loading…
Reference in New Issue
Block a user