1--all::
2Fetch all remotes.
34
-a::
5--append::
6Append ref names and object names of fetched refs to the
7existing contents of `.git/FETCH_HEAD`. Without this
8option old data in `.git/FETCH_HEAD` will be overwritten.
910
--depth=<depth>::
11Deepen the history of a 'shallow' repository created by
12`git clone` with `--depth=<depth>` option (see linkgit:git-clone[1])
13by the specified number of commits.
1415
ifndef::git-pull[]
16--dry-run::
17Show what would be done, without making any changes.
18endif::git-pull[]
1920
-f::
21--force::
22When 'git fetch' is used with `<rbranch>:<lbranch>`
23refspec, it refuses to update the local branch
24`<lbranch>` unless the remote branch `<rbranch>` it
25fetches is a descendant of `<lbranch>`. This option
26overrides that check.
2728
-k::
29--keep::
30Keep downloaded pack.
3132
ifndef::git-pull[]
33--multiple::
34Allow several <repository> and <group> arguments to be
35specified. No <refspec>s may be specified.
3637
-p::
38--prune::
39After fetching, remove any remote-tracking branches which
40no longer exist on the remote.
41endif::git-pull[]
4243
ifdef::git-pull[]
44--no-tags::
45endif::git-pull[]
46ifndef::git-pull[]
47-n::
48--no-tags::
49endif::git-pull[]
50By default, tags that point at objects that are downloaded
51from the remote repository are fetched and stored locally.
52This option disables this automatic tag following. The default
53behavior for a remote may be specified with the remote.<name>.tagopt
54setting. See linkgit:git-config[1].
5556
ifndef::git-pull[]
57-t::
58--tags::
59Most of the tags are fetched automatically as branch
60heads are downloaded, but tags that do not point at
61objects reachable from the branch heads that are being
62tracked will not be fetched by this mechanism. This
63flag lets all tags and their associated objects be
64downloaded. The default behavior for a remote may be
65specified with the remote.<name>.tagopt setting. See
66linkgit:git-config[1].
67endif::git-pull[]
6869
--[no-]recurse-submodules::
70This option controls if new commits of all populated submodules should
71be fetched too (see linkgit:git-config[1] and linkgit:gitmodules[5]).
7273
ifndef::git-pull[]
74--submodule-prefix=<path>::
75Prepend <path> to paths printed in informative messages
76such as "Fetching submodule foo". This option is used
77internally when recursing over submodules.
78endif::git-pull[]
7980
-u::
81--update-head-ok::
82By default 'git fetch' refuses to update the head which
83corresponds to the current branch. This flag disables the
84check. This is purely for the internal use for 'git pull'
85to communicate with 'git fetch', and unless you are
86implementing your own Porcelain you are not supposed to
87use it.
8889
--upload-pack <upload-pack>::
90When given, and the repository to fetch from is handled
91by 'git fetch-pack', '--exec=<upload-pack>' is passed to
92the command to specify non-default path for the command
93run on the other end.
9495
ifndef::git-pull[]
96-q::
97--quiet::
98Pass --quiet to git-fetch-pack and silence any other internally
99used git commands. Progress is not reported to the standard error
100stream.
101102
-v::
103--verbose::
104Be verbose.
105endif::git-pull[]
106107
--progress::
108Progress status is reported on the standard error stream
109by default when it is attached to a terminal, unless -q
110is specified. This flag forces progress status even if the
111standard error stream is not directed to a terminal.