Documentation/fetch-options.txt

   1 --all::
   2         Fetch all remotes.
   3
   4 -a::
   5 --append::
   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.
   9
  10 --depth=<depth>::
  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.
  14
  15 ifndef::git-pull[]
  16 --dry-run::
  17         Show what would be done, without making any changes.
  18 endif::git-pull[]
  19
  20 -f::
  21 --force::
  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
  26         overrides that check.
  27
  28 -k::
  29 --keep::
  30         Keep downloaded pack.
  31
  32 ifndef::git-pull[]
  33 --multiple::
  34         Allow several <repository> and <group> arguments to be
  35         specified. No <refspec>s may be specified.
  36
  37 -p::
  38 --prune::
  39         After fetching, remove any remote-tracking branches which
  40         no longer exist on the remote.
  41 endif::git-pull[]
  42
  43 ifdef::git-pull[]
  44 --no-tags::
  45 endif::git-pull[]
  46 ifndef::git-pull[]
  47 -n::
  48 --no-tags::
  49 endif::git-pull[]
  50         By default, tags that point at objects that are downloaded
  51         from the remote repository are fetched and stored locally.
  52         This option disables this automatic tag following. The default
  53         behavior for a remote may be specified with the remote.<name>.tagopt
  54         setting. See linkgit:git-config[1].
  55
  56 ifndef::git-pull[]
  57 -t::
  58 --tags::
  59         Most of the tags are fetched automatically as branch
  60         heads are downloaded, but tags that do not point at
  61         objects reachable from the branch heads that are being
  62         tracked will not be fetched by this mechanism.  This
  63         flag lets all tags and their associated objects be
  64         downloaded. The default behavior for a remote may be
  65         specified with the remote.<name>.tagopt setting. See
  66         linkgit:git-config[1].
  67
  68 --[no-]recurse-submodules::
  69         This option controls if new commits of all populated submodules should
  70         be fetched too (see linkgit:git-config[1] and linkgit:gitmodules[5]).
  71
  72 --submodule-prefix=<path>::
  73         Prepend <path> to paths printed in informative messages
  74         such as "Fetching submodule foo".  This option is used
  75         internally when recursing over submodules.
  76 endif::git-pull[]
  77
  78 -u::
  79 --update-head-ok::
  80         By default 'git fetch' refuses to update the head which
  81         corresponds to the current branch.  This flag disables the
  82         check.  This is purely for the internal use for 'git pull'
  83         to communicate with 'git fetch', and unless you are
  84         implementing your own Porcelain you are not supposed to
  85         use it.
  86
  87 --upload-pack <upload-pack>::
  88         When given, and the repository to fetch from is handled
  89         by 'git fetch-pack', '--exec=<upload-pack>' is passed to
  90         the command to specify non-default path for the command
  91         run on the other end.
  92
  93 ifndef::git-pull[]
  94 -q::
  95 --quiet::
  96         Pass --quiet to git-fetch-pack and silence any other internally
  97         used git commands. Progress is not reported to the standard error
  98         stream.
  99
 100 -v::
 101 --verbose::
 102         Be verbose.
 103 endif::git-pull[]
 104
 105 --progress::
 106         Progress status is reported on the standard error stream
 107         by default when it is attached to a terminal, unless -q
 108         is specified. This flag forces progress status even if the
 109         standard error stream is not directed to a terminal.