Autogenerated HTML docs for v2.26.0-51-ga7d14

1 files changed, 88 insertions, 0 deletions

diff --git a/git-pull.html b/git-pull.html
index 53be3122a..bf0f782a7 100644
--- a/git-pull.html
+++ b/git-pull.html
@@ -1260,6 +1260,14 @@ this option multiple times, one for each matching ref name.</p></div>
 documented in <a href="git-config.html">git-config(1)</a>.</p></div>

 </dd>

 <dt class="hdlist1">

+--dry-run

+</dt>

+<dd>

+<p>

+        Show what would be done, without making any changes.

+</p>

+</dd>

+<dt class="hdlist1">

 -f

 </dt>

 <dt class="hdlist1">

@@ -1286,6 +1294,25 @@ documented in <a href="git-config.html">git-config(1)</a>.</p></div>
 </p>

 </dd>

 <dt class="hdlist1">

+-p

+</dt>

+<dt class="hdlist1">

+--prune

+</dt>

+<dd>

+<p>

+        Before fetching, remove any remote-tracking references that no

+        longer exist on the remote.  Tags are not subject to pruning

+        if they are fetched only because of the default tag

+        auto-following or due to a --tags option.  However, if tags

+        are fetched due to an explicit refspec (either on the command

+        line or in the remote configuration, for example if the remote

+        was cloned with the --mirror option), then they are also

+        subject to pruning. Supplying <code>--prune-tags</code> is a shorthand for

+        providing the tag refspec.

+</p>

+</dd>

+<dt class="hdlist1">

 --no-tags

 </dt>

 <dd>

@@ -1298,6 +1325,67 @@ documented in <a href="git-config.html">git-config(1)</a>.</p></div>
 </p>

 </dd>

 <dt class="hdlist1">

+--refmap=&lt;refspec&gt;

+</dt>

+<dd>

+<p>

+        When fetching refs listed on the command line, use the

+        specified refspec (can be given more than once) to map the

+        refs to remote-tracking branches, instead of the values of

+        <code>remote.*.fetch</code> configuration variables for the remote

+        repository.  Providing an empty <code>&lt;refspec&gt;</code> to the

+        <code>--refmap</code> option causes Git to ignore the configured

+        refspecs and rely entirely on the refspecs supplied as

+        command-line arguments. See section on "Configured Remote-tracking

+        Branches" for details.

+</p>

+</dd>

+<dt class="hdlist1">

+-t

+</dt>

+<dt class="hdlist1">

+--tags

+</dt>

+<dd>

+<p>

+        Fetch all tags from the remote (i.e., fetch remote tags

+        <code>refs/tags/*</code> into local tags with the same name), in addition

+        to whatever else would otherwise be fetched.  Using this

+        option alone does not subject tags to pruning, even if --prune

+        is used (though tags may be pruned anyway if they are also the

+        destination of an explicit refspec; see <code>--prune</code>).

+</p>

+</dd>

+<dt class="hdlist1">

+-j

+</dt>

+<dt class="hdlist1">

+--jobs=&lt;n&gt;

+</dt>

+<dd>

+<p>

+        Number of parallel children to be used for all forms of fetching.

+</p>

+<div class="paragraph"><p>If the <code>--multiple</code> option was specified, the different remotes will be fetched

+in parallel. If multiple submodules are fetched, they will be fetched in

+parallel. To control them independently, use the config settings

+<code>fetch.parallel</code> and <code>submodule.fetchJobs</code> (see <a href="git-config.html">git-config(1)</a>).</p></div>

+<div class="paragraph"><p>Typically, parallel recursive and multi-remote fetches will be faster. By

+default fetches are performed sequentially, not in parallel.</p></div>

+</dd>

+<dt class="hdlist1">

+--set-upstream

+</dt>

+<dd>

+<p>

+        If the remote is fetched successfully, pull and add upstream

+        (tracking) reference, used by argument-less

+        <a href="git-pull.html">git-pull(1)</a> and other commands. For more information,

+        see <code>branch.&lt;name&gt;.merge</code> and <code>branch.&lt;name&gt;.remote</code> in

+        <a href="git-config.html">git-config(1)</a>.

+</p>

+</dd>

+<dt class="hdlist1">

 -u

 </dt>

 <dt class="hdlist1">