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].
58 Most of the tags are fetched automatically as branch
59 heads are downloaded, but tags that do not point at
60 objects reachable from the branch heads that are being
61 tracked will not be fetched by this mechanism. This
62 flag lets all tags and their associated objects be
63 downloaded. The default behavior for a remote may be
64 specified with the remote.<name>.tagopt setting. See
65 linkgit:git-config[1].
68 By default new commits of all populated submodules will be fetched
69 too. This option can be used to disable/enable recursive fetching of
70 submodules regardless of the 'fetch' configuration setting (see
71 linkgit:git-config[1] or linkgit:gitmodules[5]).
75 By default 'git fetch' refuses to update the head which
76 corresponds to the current branch. This flag disables the
77 check. This is purely for the internal use for 'git pull'
78 to communicate with 'git fetch', and unless you are
79 implementing your own Porcelain you are not supposed to
82 --upload-pack <upload-pack>::
83 When given, and the repository to fetch from is handled
84 by 'git fetch-pack', '--exec=<upload-pack>' is passed to
85 the command to specify non-default path for the command
91 Pass --quiet to git-fetch-pack and silence any other internally
92 used git commands. Progress is not reported to the standard error
101 Progress status is reported on the standard error stream
102 by default when it is attached to a terminal, unless -q
103 is specified. This flag forces progress status even if the
104 standard error stream is not directed to a terminal.