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.
38 After fetching, remove any remote tracking branches which
39 no longer exist on the remote.
49 By default, tags that point at objects that are downloaded
50 from the remote repository are fetched and stored locally.
51 This option disables this automatic tag following.
55 Most of the tags are fetched automatically as branch
56 heads are downloaded, but tags that do not point at
57 objects reachable from the branch heads that are being
58 tracked will not be fetched by this mechanism. This
59 flag lets all tags and their associated objects be
64 By default 'git-fetch' refuses to update the head which
65 corresponds to the current branch. This flag disables the
66 check. This is purely for the internal use for 'git-pull'
67 to communicate with 'git-fetch', and unless you are
68 implementing your own Porcelain you are not supposed to
71 --upload-pack <upload-pack>::
72 When given, and the repository to fetch from is handled
73 by 'git-fetch-pack', '--exec=<upload-pack>' is passed to
74 the command to specify non-default path for the command
80 Pass --quiet to git-fetch-pack and silence any other internally