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