Documentation/fetch-options.txt

   1 -q, \--quiet::
   2         Pass --quiet to git-fetch-pack and silence any other internally
   3         used programs.
   4
   5 -v, \--verbose::
   6         Be verbose.
   7
   8 -a, \--append::
   9         Append ref names and object names of fetched refs to the
  10         existing contents of `.git/FETCH_HEAD`.  Without this
  11         option old data in `.git/FETCH_HEAD` will be overwritten.
  12
  13 \--upload-pack <upload-pack>::
  14         When given, and the repository to fetch from is handled
  15         by 'git-fetch-pack', '--exec=<upload-pack>' is passed to
  16         the command to specify non-default path for the command
  17         run on the other end.
  18
  19 -f, \--force::
  20         When `git-fetch` is used with `<rbranch>:<lbranch>`
  21         refspec, it refuses to update the local branch
  22         `<lbranch>` unless the remote branch `<rbranch>` it
  23         fetches is a descendant of `<lbranch>`.  This option
  24         overrides that check.
  25
  26 -n, \--no-tags::
  27         By default, `git-fetch` fetches tags that point at
  28         objects that are downloaded from the remote repository
  29         and stores them locally.  This option disables this
  30         automatic tag following.
  31
  32 -t, \--tags::
  33         Most of the tags are fetched automatically as branch
  34         heads are downloaded, but tags that do not point at
  35         objects reachable from the branch heads that are being
  36         tracked will not be fetched by this mechanism.  This
  37         flag lets all tags and their associated objects be
  38         downloaded.
  39
  40 -k, \--keep::
  41         Keep downloaded pack.
  42
  43 -u, \--update-head-ok::
  44         By default `git-fetch` refuses to update the head which
  45         corresponds to the current branch.  This flag disables the
  46         check.  This is purely for the internal use for `git-pull`
  47         to communicate with `git-fetch`, and unless you are
  48         implementing your own Porcelain you are not supposed to
  49         use it.
  50
  51 \--depth=<depth>::
  52         Deepen the history of a 'shallow' repository created by
  53         `git clone` with `--depth=<depth>` option (see gitlink:git-clone[1])
  54         by the specified number of commits.