Documentation/config/fetch.txt

   1 fetch.recurseSubmodules::
   2         This option controls whether `git fetch` (and the underlying fetch
   3         in `git pull`) will recursively fetch into populated submodules.
   4         This option can be set either to a boolean value or to 'on-demand'.
   5         Setting it to a boolean changes the behavior of fetch and pull to
   6         recurse unconditionally into submodules when set to true or to not
   7         recurse at all when set to false. When set to 'on-demand', fetch and
   8         pull will only recurse into a populated submodule when its
   9         superproject retrieves a commit that updates the submodule's
  10         reference.
  11         Defaults to 'on-demand', or to the value of 'submodule.recurse' if set.
  12
  13 fetch.fsckObjects::
  14         If it is set to true, git-fetch-pack will check all fetched
  15         objects. See `transfer.fsckObjects` for what's
  16         checked. Defaults to false. If not set, the value of
  17         `transfer.fsckObjects` is used instead.
  18
  19 fetch.fsck.<msg-id>::
  20         Acts like `fsck.<msg-id>`, but is used by
  21         linkgit:git-fetch-pack[1] instead of linkgit:git-fsck[1]. See
  22         the `fsck.<msg-id>` documentation for details.
  23
  24 fetch.fsck.skipList::
  25         Acts like `fsck.skipList`, but is used by
  26         linkgit:git-fetch-pack[1] instead of linkgit:git-fsck[1]. See
  27         the `fsck.skipList` documentation for details.
  28
  29 fetch.unpackLimit::
  30         If the number of objects fetched over the Git native
  31         transfer is below this
  32         limit, then the objects will be unpacked into loose object
  33         files. However if the number of received objects equals or
  34         exceeds this limit then the received pack will be stored as
  35         a pack, after adding any missing delta bases.  Storing the
  36         pack from a push can make the push operation complete faster,
  37         especially on slow filesystems.  If not set, the value of
  38         `transfer.unpackLimit` is used instead.
  39
  40 fetch.prune::
  41         If true, fetch will automatically behave as if the `--prune`
  42         option was given on the command line.  See also `remote.<name>.prune`
  43         and the PRUNING section of linkgit:git-fetch[1].
  44
  45 fetch.pruneTags::
  46         If true, fetch will automatically behave as if the
  47         `refs/tags/*:refs/tags/*` refspec was provided when pruning,
  48         if not set already. This allows for setting both this option
  49         and `fetch.prune` to maintain a 1=1 mapping to upstream
  50         refs. See also `remote.<name>.pruneTags` and the PRUNING
  51         section of linkgit:git-fetch[1].
  52
  53 fetch.output::
  54         Control how ref update status is printed. Valid values are
  55         `full` and `compact`. Default value is `full`. See section
  56         OUTPUT in linkgit:git-fetch[1] for detail.
  57
  58 fetch.negotiationAlgorithm::
  59         Control how information about the commits in the local repository is
  60         sent when negotiating the contents of the packfile to be sent by the
  61         server. Set to "skipping" to use an algorithm that skips commits in an
  62         effort to converge faster, but may result in a larger-than-necessary
  63         packfile; or set to "noop" to not send any information at all, which
  64         will almost certainly result in a larger-than-necessary packfile, but
  65         will skip the negotiation step.
  66         The default is "default" which instructs Git to use the default algorithm
  67         that never skips commits (unless the server has acknowledged it or one
  68         of its descendants). If `feature.experimental` is enabled, then this
  69         setting defaults to "skipping".
  70         Unknown values will cause 'git fetch' to error out.
  71 +
  72 See also the `--negotiate-only` and `--negotiation-tip` options to
  73 linkgit:git-fetch[1].
  74
  75 fetch.showForcedUpdates::
  76         Set to false to enable `--no-show-forced-updates` in
  77         linkgit:git-fetch[1] and linkgit:git-pull[1] commands.
  78         Defaults to true.
  79
  80 fetch.parallel::
  81         Specifies the maximal number of fetch operations to be run in parallel
  82         at a time (submodules, or remotes when the `--multiple` option of
  83         linkgit:git-fetch[1] is in effect).
  84 +
  85 A value of 0 will give some reasonable default. If unset, it defaults to 1.
  86 +
  87 For submodules, this setting can be overridden using the `submodule.fetchJobs`
  88 config setting.
  89
  90 fetch.writeCommitGraph::
  91         Set to true to write a commit-graph after every `git fetch` command
  92         that downloads a pack-file from a remote. Using the `--split` option,
  93         most executions will create a very small commit-graph file on top of
  94         the existing commit-graph file(s). Occasionally, these files will
  95         merge and the write may take longer. Having an updated commit-graph
  96         file helps performance of many Git commands, including `git merge-base`,
  97         `git push -f`, and `git log --graph`. Defaults to false.