Documentation / fetch-options.txton commit Documentation: fix typos / spelling mistakes (680ebc0)
   1-q::
   2--quiet::
   3        Pass --quiet to git-fetch-pack and silence any other internally
   4        used programs.
   5
   6-v::
   7--verbose::
   8        Be verbose.
   9
  10-a::
  11--append::
  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.
  15
  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
  20        run on the other end.
  21
  22-f::
  23--force::
  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
  28        overrides that check.
  29
  30ifdef::git-pull[]
  31--no-tags::
  32endif::git-pull[]
  33ifndef::git-pull[]
  34-n::
  35--no-tags::
  36endif::git-pull[]
  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.
  40
  41-t::
  42--tags::
  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
  48        downloaded.
  49
  50-k::
  51--keep::
  52        Keep downloaded pack.
  53
  54-u::
  55--update-head-ok::
  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
  61        use it.
  62
  63--depth=<depth>::
  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.