3 Pass --quiet to git-fetch-pack and silence any other internally
12 Append ref names and object names of fetched refs to the
13 existing contents of `.git/FETCH_HEAD`. Without this
14 option old data in `.git/FETCH_HEAD` will be overwritten.
16 --upload-pack <upload-pack>::
17 When given, and the repository to fetch from is handled
18 by 'git-fetch-pack', '--exec=<upload-pack>' is passed to
19 the command to specify non-default path for the command
24 When `git-fetch` is used with `<rbranch>:<lbranch>`
25 refspec, it refuses to update the local branch
26 `<lbranch>` unless the remote branch `<rbranch>` it
27 fetches is a descendant of `<lbranch>`. This option
37 By default, tags that point at objects that are downloaded
38 from the remote repository are fetched and stored locally.
39 This option disables this automatic tag following.
43 Most of the tags are fetched automatically as branch
44 heads are downloaded, but tags that do not point at
45 objects reachable from the branch heads that are being
46 tracked will not be fetched by this mechanism. This
47 flag lets all tags and their associated objects be
56 By default `git-fetch` refuses to update the head which
57 corresponds to the current branch. This flag disables the
58 check. This is purely for the internal use for `git-pull`
59 to communicate with `git-fetch`, and unless you are
60 implementing your own Porcelain you are not supposed to
64 Deepen the history of a 'shallow' repository created by
65 `git clone` with `--depth=<depth>` option (see linkgit:git-clone[1])
66 by the specified number of commits.