diff options
Diffstat (limited to 'git-fetch.html')
| -rw-r--r-- | git-fetch.html | 168 |
1 files changed, 167 insertions, 1 deletions
diff --git a/git-fetch.html b/git-fetch.html index f52b984da..e4fc99601 100644 --- a/git-fetch.html +++ b/git-fetch.html @@ -1993,6 +1993,172 @@ As in #1, the attacker chooses an object ID X to steal. The victim sends </div>
</div>
<div class="sect1">
+<h2 id="_configuration">CONFIGURATION</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Everything below this line in this section is selectively included
+from the <a href="git-config.html">git-config(1)</a> documentation. The content is the same
+as what’s found there:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+fetch.recurseSubmodules
+</dt>
+<dd>
+<p>
+ This option controls whether <code>git fetch</code> (and the underlying fetch
+ in <code>git pull</code>) will recursively fetch into populated submodules.
+ This option can be set either to a boolean value or to <em>on-demand</em>.
+ Setting it to a boolean changes the behavior of fetch and pull to
+ recurse unconditionally into submodules when set to true or to not
+ recurse at all when set to false. When set to <em>on-demand</em>, fetch and
+ pull will only recurse into a populated submodule when its
+ superproject retrieves a commit that updates the submodule’s
+ reference.
+ Defaults to <em>on-demand</em>, or to the value of <em>submodule.recurse</em> if set.
+</p>
+</dd>
+<dt class="hdlist1">
+fetch.fsckObjects
+</dt>
+<dd>
+<p>
+ If it is set to true, git-fetch-pack will check all fetched
+ objects. See <code>transfer.fsckObjects</code> for what’s
+ checked. Defaults to false. If not set, the value of
+ <code>transfer.fsckObjects</code> is used instead.
+</p>
+</dd>
+<dt class="hdlist1">
+fetch.fsck.<msg-id>
+</dt>
+<dd>
+<p>
+ Acts like <code>fsck.<msg-id></code>, but is used by
+ <a href="git-fetch-pack.html">git-fetch-pack(1)</a> instead of <a href="git-fsck.html">git-fsck(1)</a>. See
+ the <code>fsck.<msg-id></code> documentation for details.
+</p>
+</dd>
+<dt class="hdlist1">
+fetch.fsck.skipList
+</dt>
+<dd>
+<p>
+ Acts like <code>fsck.skipList</code>, but is used by
+ <a href="git-fetch-pack.html">git-fetch-pack(1)</a> instead of <a href="git-fsck.html">git-fsck(1)</a>. See
+ the <code>fsck.skipList</code> documentation for details.
+</p>
+</dd>
+<dt class="hdlist1">
+fetch.unpackLimit
+</dt>
+<dd>
+<p>
+ If the number of objects fetched over the Git native
+ transfer is below this
+ limit, then the objects will be unpacked into loose object
+ files. However if the number of received objects equals or
+ exceeds this limit then the received pack will be stored as
+ a pack, after adding any missing delta bases. Storing the
+ pack from a push can make the push operation complete faster,
+ especially on slow filesystems. If not set, the value of
+ <code>transfer.unpackLimit</code> is used instead.
+</p>
+</dd>
+<dt class="hdlist1">
+fetch.prune
+</dt>
+<dd>
+<p>
+ If true, fetch will automatically behave as if the <code>--prune</code>
+ option was given on the command line. See also <code>remote.<name>.prune</code>
+ and the PRUNING section of <a href="git-fetch.html">git-fetch(1)</a>.
+</p>
+</dd>
+<dt class="hdlist1">
+fetch.pruneTags
+</dt>
+<dd>
+<p>
+ If true, fetch will automatically behave as if the
+ <code>refs/tags/*:refs/tags/*</code> refspec was provided when pruning,
+ if not set already. This allows for setting both this option
+ and <code>fetch.prune</code> to maintain a 1=1 mapping to upstream
+ refs. See also <code>remote.<name>.pruneTags</code> and the PRUNING
+ section of <a href="git-fetch.html">git-fetch(1)</a>.
+</p>
+</dd>
+<dt class="hdlist1">
+fetch.output
+</dt>
+<dd>
+<p>
+ Control how ref update status is printed. Valid values are
+ <code>full</code> and <code>compact</code>. Default value is <code>full</code>. See section
+ OUTPUT in <a href="git-fetch.html">git-fetch(1)</a> for detail.
+</p>
+</dd>
+<dt class="hdlist1">
+fetch.negotiationAlgorithm
+</dt>
+<dd>
+<p>
+ Control how information about the commits in the local repository
+ is sent when negotiating the contents of the packfile to be sent by
+ the server. Set to "consecutive" to use an algorithm that walks
+ over consecutive commits checking each one. Set to "skipping" to
+ use an algorithm that skips commits in an effort to converge
+ faster, but may result in a larger-than-necessary packfile; or set
+ to "noop" to not send any information at all, which will almost
+ certainly result in a larger-than-necessary packfile, but will skip
+ the negotiation step. Set to "default" to override settings made
+ previously and use the default behaviour. The default is normally
+ "consecutive", but if <code>feature.experimental</code> is true, then the
+ default is "skipping". Unknown values will cause <em>git fetch</em> to
+ error out.
+</p>
+<div class="paragraph"><p>See also the <code>--negotiate-only</code> and <code>--negotiation-tip</code> options to
+<a href="git-fetch.html">git-fetch(1)</a>.</p></div>
+</dd>
+<dt class="hdlist1">
+fetch.showForcedUpdates
+</dt>
+<dd>
+<p>
+ Set to false to enable <code>--no-show-forced-updates</code> in
+ <a href="git-fetch.html">git-fetch(1)</a> and <a href="git-pull.html">git-pull(1)</a> commands.
+ Defaults to true.
+</p>
+</dd>
+<dt class="hdlist1">
+fetch.parallel
+</dt>
+<dd>
+<p>
+ Specifies the maximal number of fetch operations to be run in parallel
+ at a time (submodules, or remotes when the <code>--multiple</code> option of
+ <a href="git-fetch.html">git-fetch(1)</a> is in effect).
+</p>
+<div class="paragraph"><p>A value of 0 will give some reasonable default. If unset, it defaults to 1.</p></div>
+<div class="paragraph"><p>For submodules, this setting can be overridden using the <code>submodule.fetchJobs</code>
+config setting.</p></div>
+</dd>
+<dt class="hdlist1">
+fetch.writeCommitGraph
+</dt>
+<dd>
+<p>
+ Set to true to write a commit-graph after every <code>git fetch</code> command
+ that downloads a pack-file from a remote. Using the <code>--split</code> option,
+ most executions will create a very small commit-graph file on top of
+ the existing commit-graph file(s). Occasionally, these files will
+ merge and the write may take longer. Having an updated commit-graph
+ file helps performance of many Git commands, including <code>git merge-base</code>,
+ <code>git push -f</code>, and <code>git log --graph</code>. Defaults to false.
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+<div class="sect1">
<h2 id="_bugs">BUGS</h2>
<div class="sectionbody">
<div class="paragraph"><p>Using --recurse-submodules can only fetch new commits in submodules that are
@@ -2018,7 +2184,7 @@ submodule update</code>. This is expected to be fixed in a future Git version.</ <div id="footer">
<div id="footer-text">
Last updated
- 2022-03-27 10:29:17 PDT
+ 2022-09-14 13:23:11 PDT
</div>
</div>
</body>
|