Documentation / fetch-options.txton commit sha1-lookup: make selection of 'middle' less aggressive (12ecb01)
   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
  26ifdef::git-pull[]
  27\--no-tags::
  28endif::git-pull[]
  29ifndef::git-pull[]
  30-n, \--no-tags::
  31endif::git-pull[]
  32        By default, tags that point at objects that are downloaded
  33        from the remote repository are fetched and stored locally.
  34        This option disables this automatic tag following.
  35
  36-t, \--tags::
  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
  42        downloaded.
  43
  44-k, \--keep::
  45        Keep downloaded pack.
  46
  47-u, \--update-head-ok::
  48        By default `git-fetch` refuses to update the head which
  49        corresponds to the current branch.  This flag disables the
  50        check.  This is purely for the internal use for `git-pull`
  51        to communicate with `git-fetch`, and unless you are
  52        implementing your own Porcelain you are not supposed to
  53        use it.
  54
  55\--depth=<depth>::
  56        Deepen the history of a 'shallow' repository created by
  57        `git clone` with `--depth=<depth>` option (see linkgit:git-clone[1])
  58        by the specified number of commits.