Autogenerated HTML docs for v2.44.0-325-g11c82

1 files changed, 22 insertions, 23 deletions

diff --git a/git-clone.html b/git-clone.html
index 6e42518f8..8195bf02c 100644
--- a/git-clone.html
+++ b/git-clone.html
@@ -862,9 +862,9 @@ objects from the source repository into a pack in the cloned repository.</p></di
 </dt>

 <dd>

 <p>

-        If the reference repository is on the local machine,

+        If the reference <em>&lt;repository&gt;</em> is on the local machine,

         automatically setup <code>.git/objects/info/alternates</code> to

-        obtain objects from the reference repository.  Using

+        obtain objects from the reference <em>&lt;repository&gt;</em>.  Using

         an already existing repository as an alternate will

         require fewer objects to be copied from the repository

         being cloned, reducing network and local storage costs.

@@ -956,7 +956,7 @@ objects from the source repository into a pack in the cloned repository.</p></di
 <dd>

 <p>

         Fail if the source repository is a shallow repository.

-        The <em>clone.rejectShallow</em> configuration variable can be used to

+        The <code>clone.rejectShallow</code> configuration variable can be used to

         specify the default.

 </p>

 </dd>

@@ -966,8 +966,8 @@ objects from the source repository into a pack in the cloned repository.</p></di
 <dd>

 <p>

         Make a <em>bare</em> Git repository.  That is, instead of

-        creating <code>&lt;directory&gt;</code> and placing the administrative

-        files in <code>&lt;directory&gt;/.git</code>, make the <code>&lt;directory&gt;</code>

+        creating <em>&lt;directory&gt;</em> and placing the administrative

+        files in <code>&lt;directory&gt;/.git</code>, make the <em>&lt;directory&gt;</em>

         itself the <code>$GIT_DIR</code>. This obviously implies the <code>--no-checkout</code>

         because there is nowhere to check out the working tree.

         Also the branch heads at the remote are copied directly

@@ -995,11 +995,11 @@ objects from the source repository into a pack in the cloned repository.</p></di
 <p>

         Use the partial clone feature and request that the server sends

         a subset of reachable objects according to a given object filter.

-        When using <code>--filter</code>, the supplied <code>&lt;filter-spec&gt;</code> is used for

+        When using <code>--filter</code>, the supplied <em>&lt;filter-spec&gt;</em> is used for

         the partial clone filter. For example, <code>--filter=blob:none</code> will

         filter out all blobs (file contents) until needed by Git. Also,

         <code>--filter=blob:limit=&lt;size&gt;</code> will filter out all blobs of size

-        at least <code>&lt;size&gt;</code>. For more details on filter specifications, see

+        at least <em>&lt;size&gt;</em>. For more details on filter specifications, see

         the <code>--filter</code> option in <a href="git-rev-list.html">git-rev-list(1)</a>.

 </p>

 </dd>

@@ -1035,7 +1035,7 @@ objects from the source repository into a pack in the cloned repository.</p></di
 <dd>

 <p>

         Instead of using the remote name <code>origin</code> to keep track of the upstream

-        repository, use <code>&lt;name&gt;</code>.  Overrides <code>clone.defaultRemoteName</code> from the

+        repository, use <em>&lt;name&gt;</em>.  Overrides <code>clone.defaultRemoteName</code> from the

         config.

 </p>

 </dd>

@@ -1048,7 +1048,7 @@ objects from the source repository into a pack in the cloned repository.</p></di
 <dd>

 <p>

         Instead of pointing the newly created HEAD to the branch pointed

-        to by the cloned repository&#8217;s HEAD, point to <code>&lt;name&gt;</code> branch

+        to by the cloned repository&#8217;s HEAD, point to <em>&lt;name&gt;</em> branch

         instead. In a non-bare repository, this is the branch that will

         be checked out.

         <code>--branch</code> can also take tags and detaches the HEAD at that commit

@@ -1088,7 +1088,7 @@ objects from the source repository into a pack in the cloned repository.</p></di
         Set a configuration variable in the newly-created repository;

         this takes effect immediately after the repository is

         initialized, but before the remote history is fetched or any

-        files checked out.  The key is in the same format as expected by

+        files checked out.  The <em>&lt;key&gt;</em> is in the same format as expected by

         <a href="git-config.html">git-config(1)</a> (e.g., <code>core.eol=true</code>). If multiple

         values are given for the same key, each value will be written to

         the config file. This makes it safe, for example, to add

@@ -1140,7 +1140,7 @@ corresponding <code>--mirror</code> and <code>--no-tags</code> options instead.<
         branch remote&#8217;s <code>HEAD</code> points at.

         Further fetches into the resulting repository will only update the

         remote-tracking branch for the branch this option was used for the

-        initial cloning.  If the HEAD at the remote did not point at any

+        initial cloning.  If the <code>HEAD</code> at the remote did not point at any

         branch when <code>--single-branch</code> clone was made, no remote-tracking

         branch is created.

 </p>

@@ -1167,7 +1167,7 @@ branch of some repository for search indexing.</p></div>
 <dd>

 <p>

         After the clone is created, initialize and clone submodules

-        within based on the provided pathspec.  If no pathspec is

+        within based on the provided <em>&lt;pathspec&gt;</em>.  If no <em>=&lt;pathspec&gt;</em> is

         provided, all submodules are initialized and cloned.

         This option can be given multiple times for pathspecs consisting

         of multiple entries.  The resulting clone has <code>submodule.active</code> set to

@@ -1250,7 +1250,7 @@ Specify the given ref storage format for the repository. The valid values are:
 </dt>

 <dd>

 <p>

-        The (possibly remote) repository to clone from.  See the

+        The (possibly remote) <em>&lt;repository&gt;</em> to clone from.  See the

         <a href="#URLS">GIT URLS</a> section below for more information on specifying

         repositories.

 </p>

@@ -1261,7 +1261,7 @@ Specify the given ref storage format for the repository. The valid values are:
 <dd>

 <p>

         The name of a new directory to clone into.  The "humanish"

-        part of the source repository is used if no directory is

+        part of the source repository is used if no <em>&lt;directory&gt;</em> is

         explicitly given (<code>repo</code> for <code>/path/to/repo.git</code> and <code>foo</code>

         for <code>host.xz:foo/.git</code>).  Cloning into an existing directory

         is only allowed if the directory is empty.

@@ -1273,7 +1273,7 @@ Specify the given ref storage format for the repository. The valid values are:
 <dd>

 <p>

         Before fetching from the remote, fetch a bundle from the given

-        <code>&lt;uri&gt;</code> and unbundle the data into the local repository. The refs

+        <em>&lt;uri&gt;</em> and unbundle the data into the local repository. The refs

         in the bundle will be stored under the hidden <code>refs/bundle/*</code>

         namespace. This option is incompatible with <code>--depth</code>,

         <code>--shallow-since</code>, and <code>--shallow-exclude</code>.

@@ -1363,21 +1363,21 @@ file:///path/to/repo.git/
 </li>

 </ul></div>

 <div class="paragraph"><p>These two syntaxes are mostly equivalent, except the former implies

---local option.</p></div>

-<div class="paragraph"><p><em>git clone</em>, <em>git fetch</em> and <em>git pull</em>, but not <em>git push</em>, will also

+<code>--local</code> option.</p></div>

+<div class="paragraph"><p><code>git clone</code>, <code>git fetch</code> and <code>git pull</code>, but not <code>git push</code>, will also

 accept a suitable bundle file. See <a href="git-bundle.html">git-bundle(1)</a>.</p></div>

 <div class="paragraph"><p>When Git doesn&#8217;t know how to handle a certain transport protocol, it

-attempts to use the <em>remote-&lt;transport&gt;</em> remote helper, if one

+attempts to use the <code>remote-&lt;transport&gt;</code> remote helper, if one

 exists. To explicitly request a remote helper, the following syntax

 may be used:</p></div>

 <div class="ulist"><ul>

 <li>

 <p>

-&lt;transport&gt;::&lt;address&gt;

+<em>&lt;transport&gt;</em>::_&lt;address&gt;_

 </p>

 </li>

 </ul></div>

-<div class="paragraph"><p>where &lt;address&gt; may be a path, a server and path, or an arbitrary

+<div class="paragraph"><p>where <em>&lt;address&gt;</em> may be a path, a server and path, or an arbitrary

 URL-like string recognized by the specific remote helper being

 invoked. See <a href="gitremote-helpers.html">gitremote-helpers(7)</a> for details.</p></div>

 <div class="paragraph"><p>If there are a large number of similarly-named remote repositories and

@@ -1478,8 +1478,7 @@ init.templateDir
 </dt>

 <dd>

 <p>

-        Specify the directory from which templates will be copied.

-        (See the "TEMPLATE DIRECTORY" section of <a href="git-init.html">git-init(1)</a>.)

+        Specify the directory from which templates will be copied. (See the "TEMPLATE DIRECTORY" section of <a href="git-init.html">git-init(1)</a>.)

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1534,7 +1533,7 @@ clone.filterSubmodules
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2024-03-01 17:30:58 PST

+ 2024-03-21 16:28:38 PDT

 </div>

 </div>

 </body>