6 Append ref names and object names of fetched refs to the
7 existing contents of `.git/FETCH_HEAD`. Without this
8 option old data in `.git/FETCH_HEAD` will be overwritten.
11 Deepen the history of a 'shallow' repository created by
12 `git clone` with `--depth=<depth>` option (see linkgit:git-clone[1])
13 by the specified number of commits.
17 Show what would be done, without making any changes.
22 When 'git fetch' is used with `<rbranch>:<lbranch>`
23 refspec, it refuses to update the local branch
24 `<lbranch>` unless the remote branch `<rbranch>` it
25 fetches is a descendant of `<lbranch>`. This option
34 Allow several <repository> and <group> arguments to be
35 specified. No <refspec>s may be specified.
39 After fetching, remove any remote-tracking branches which
40 no longer exist on the remote.
50 By default, tags that point at objects that are downloaded
51 from the remote repository are fetched and stored locally.
52 This option disables this automatic tag following. The default
53 behavior for a remote may be specified with the remote.<name>.tagopt
54 setting. See linkgit:git-config[1].
59 Most of the tags are fetched automatically as branch
60 heads are downloaded, but tags that do not point at
61 objects reachable from the branch heads that are being
62 tracked will not be fetched by this mechanism. This
63 flag lets all tags and their associated objects be
64 downloaded. The default behavior for a remote may be
65 specified with the remote.<name>.tagopt setting. See
66 linkgit:git-config[1].
68 --recurse-submodules[=yes|on-demand|no]::
69 This option controls if and under what conditions new commits of
70 populated submodules should be fetched too. It can be used as a
71 boolean option to completely disable recursion when set to 'no' or to
72 unconditionally recurse into all populated submodules when set to
73 'yes', which is the default when this option is used without any
74 value. Use 'on-demand' to only recurse into a populated submodule
75 when the superproject retrieves a commit that updates the submodule's
78 --no-recurse-submodules::
79 Disable recursive fetching of submodules (this has the same effect as
80 using the '--recurse-submodules=no' option).
82 --submodule-prefix=<path>::
83 Prepend <path> to paths printed in informative messages
84 such as "Fetching submodule foo". This option is used
85 internally when recursing over submodules.
87 --recurse-submodules-default=[yes|on-demand]::
88 This option is used internally to temporarily provide a
89 non-negative default value for the --recurse-submodules
90 option. All other methods of configuring fetch's submodule
91 recursion (such as settings in linkgit:gitmodules[5] and
92 linkgit:git-config[1]) override this option, as does
93 specifying --[no-]recurse-submodules directly.
98 By default 'git fetch' refuses to update the head which
99 corresponds to the current branch. This flag disables the
100 check. This is purely for the internal use for 'git pull'
101 to communicate with 'git fetch', and unless you are
102 implementing your own Porcelain you are not supposed to
105 --upload-pack <upload-pack>::
106 When given, and the repository to fetch from is handled
107 by 'git fetch-pack', '--exec=<upload-pack>' is passed to
108 the command to specify non-default path for the command
109 run on the other end.
114 Pass --quiet to git-fetch-pack and silence any other internally
115 used git commands. Progress is not reported to the standard error
124 Progress status is reported on the standard error stream
125 by default when it is attached to a terminal, unless -q
126 is specified. This flag forces progress status even if the
127 standard error stream is not directed to a terminal.