Update manual pages (manually forced rebuild)

Updated via the `update-git-version-and-manual-pages.yml` GitHub workflow.

Author: dscho

external/docs/content/docs/BreakingChanges.html

@@ -229,7 +229,7 @@ <h3 id="_removals"><a class="anchor" href="#_removals"></a>Removals</h3>
 that complaint did not cause us to reverse course. On the contrary, we have
 doubled down on the deprecation and starting with 4406522b76 (pack-redundant:
 escalate deprecation warning to an error, 2023-03-23), the command dies unless
-the user passes the <code>--i-still-use-this</code> option.</p>
+the user passes the <span class='synopsis'><code>--i-still-use-this</code></span> option.</p>
 </div>
 <div class="paragraph">
 <p>There have not been any subsequent complaints, so this command will finally be

external/docs/content/docs/BreakingChanges/2.47.0.html

@@ -208,7 +208,7 @@ <h3 id="_removals"><a class="anchor" href="#_removals"></a>Removals</h3>
 that complaint did not cause us to reverse course. On the contrary, we have
 doubled down on the deprecation and starting with 4406522b76 (pack-redundant:
 escalate deprecation warning to an error, 2023-03-23), the command dies unless
-the user passes the <code>--i-still-use-this</code> option.</p>
+the user passes the <span class='synopsis'><code>--i-still-use-this</code></span> option.</p>
 </div>
 <div class="paragraph">
 <p>There have not been any subsequent complaints, so this command will finally be

external/docs/content/docs/BreakingChanges/2.48.0.html

@@ -131,7 +131,7 @@ <h2 id="_git_3_0"><a class="anchor" href="#_git_3_0"></a>Git 3.0</h2>
 <div class="paragraph">
 <p>The following subsections document upcoming breaking changes for Git 3.0. There
 is no planned release date for this breaking version yet.  The early
-adopter configuration used for changes for this release is <code>feature.git3</code>.</p>
+adopter configuration used for changes for this release is <span class='synopsis'><code>feature.git3</code></span>.</p>
 </div>
 <div class="paragraph">
 <p>Proposed changes and removals only include items which are "ready" to be done.
@@ -230,7 +230,7 @@ <h3 id="_removals"><a class="anchor" href="#_removals"></a>Removals</h3>
 that complaint did not cause us to reverse course. On the contrary, we have
 doubled down on the deprecation and starting with 4406522b76 (pack-redundant:
 escalate deprecation warning to an error, 2023-03-23), the command dies unless
-the user passes the <code>--i-still-use-this</code> option.</p>
+the user passes the <span class='synopsis'><code>--i-still-use-this</code></span> option.</p>
 </div>
 <div class="paragraph">
 <p>There have not been any subsequent complaints, so this command will finally be

external/docs/content/docs/BreakingChanges/2.49.0.html

@@ -228,7 +228,7 @@ <h3 id="_removals"><a class="anchor" href="#_removals"></a>Removals</h3>
 that complaint did not cause us to reverse course. On the contrary, we have
 doubled down on the deprecation and starting with 4406522b76 (pack-redundant:
 escalate deprecation warning to an error, 2023-03-23), the command dies unless
-the user passes the <code>--i-still-use-this</code> option.</p>
+the user passes the <span class='synopsis'><code>--i-still-use-this</code></span> option.</p>
 </div>
 <div class="paragraph">
 <p>There have not been any subsequent complaints, so this command will finally be

external/docs/content/docs/BreakingChanges/2.50.0.html

@@ -228,7 +228,7 @@ <h3 id="_removals"><a class="anchor" href="#_removals"></a>Removals</h3>
 that complaint did not cause us to reverse course. On the contrary, we have
 doubled down on the deprecation and starting with 4406522b76 (pack-redundant:
 escalate deprecation warning to an error, 2023-03-23), the command dies unless
-the user passes the <code>--i-still-use-this</code> option.</p>
+the user passes the <span class='synopsis'><code>--i-still-use-this</code></span> option.</p>
 </div>
 <div class="paragraph">
 <p>There have not been any subsequent complaints, so this command will finally be

external/docs/content/docs/CodingGuidelines.html

@@ -866,15 +866,16 @@
 </li>
 <li>
 <p>You can launch gdb around your program using the shorthand GIT_DEBUGGER.
-Run <code>GIT_DEBUGGER=1 ./bin-wrappers/git foo</code> to simply use gdb as is, or
-run <code>GIT_DEBUGGER="&lt;debugger&gt; &lt;debugger-args&gt;" ./bin-wrappers/git foo</code> to
-use your own debugger and arguments. Example: <code>GIT_DEBUGGER="ddd --gdb"
-./bin-wrappers/git log</code> (See <code>bin-wrappers/wrap-for-bin.sh</code>.)</p>
+Run <span class='synopsis'><code>GIT_DEBUGGER=1</code> <code>./bin-wrappers/git</code> <code>foo</code></span> to simply use gdb as is, or
+run <span class='synopsis'><code>GIT_DEBUGGER="</code><em>&lt;debugger&gt;</em> <em>&lt;debugger-args&gt;</em><code>"</code> <code>./bin-wrappers/git</code> <code>foo</code></span> to
+use your own debugger and arguments. Example: <span class='synopsis'><code>GIT_DEBUGGER="ddd</code> <code>--gdb"</code>
+
+<code>./bin-wrappers/git</code> <code>log</code></span> (See <span class='synopsis'><code>bin-wrappers/wrap-for-bin.sh</code></span>.)</p>
 </li>
 <li>
 <p>The primary data structure that a subsystem <em>S</em> deals with is called
-<code>struct S</code>. Functions that operate on <code>struct S</code> are named
-<code>S_&lt;verb&gt;()</code> and should generally receive a pointer to <code>struct S</code> as
+<span class='synopsis'><code>struct</code> <code>S</code></span>. Functions that operate on <span class='synopsis'><code>struct</code> <code>S</code></span> are named
+<span class='synopsis'><code>S_</code><em>&lt;verb&gt;</em>()</span> and should generally receive a pointer to <span class='synopsis'><code>struct</code> <code>S</code></span> as
 first parameter. E.g.</p>
 <div class="literalblock">
 <div class="content">
@@ -914,24 +915,24 @@
 </li>
 <li>
 <p>There are several common idiomatic names for functions performing
-specific tasks on a structure <code>S</code>:</p>
+specific tasks on a structure <span class='synopsis'><code>S</code></span>:</p>
 </li>
 <li>
-<p><code>S_init()</code> initializes a structure without allocating the
+<p><span class='synopsis'><code>S_init</code>()</span> initializes a structure without allocating the
 structure itself.</p>
 </li>
 <li>
-<p><code>S_release()</code> releases a structure&#8217;s contents without freeing the
+<p><span class='synopsis'><code>S_release</code>()</span> releases a structure&#8217;s contents without freeing the
 structure.</p>
 </li>
 <li>
-<p><code>S_clear()</code> is equivalent to <code>S_release()</code> followed by <code>S_init()</code>
+<p><span class='synopsis'><code>S_clear</code>()</span> is equivalent to <span class='synopsis'><code>S_release</code>()</span> followed by <span class='synopsis'><code>S_init</code>()</span>
 such that the structure is directly usable after clearing it. When
-<code>S_clear()</code> is provided, <code>S_init()</code> shall not allocate resources
+<span class='synopsis'><code>S_clear</code>()</span> is provided, <span class='synopsis'><code>S_init</code>()</span> shall not allocate resources
 that need to be released again.</p>
 </li>
 <li>
-<p><code>S_free()</code> releases a structure&#8217;s contents and frees the
+<p><span class='synopsis'><code>S_free</code>()</span> releases a structure&#8217;s contents and frees the
 structure.</p>
 </li>
 <li>
@@ -1093,17 +1094,17 @@
 </li>
 <li>
 <p>Enclose the subject of an error inside a pair of single quotes,
-e.g. <code>die(_("unable to open '%s'"), path)</code>.</p>
+e.g. <span class='synopsis'><code>die</code>(<code>_</code>(<code>"unable</code> <code>to</code> <code>open</code> <code>%s'"</code>)<code>,</code> <code>path</code>)</span>.</p>
 </li>
 <li>
 <p>Unless there is a compelling reason not to, error messages from
 porcelain commands should be marked for translation, e.g.
-<code>die(_("bad revision %s"), revision)</code>.</p>
+<span class='synopsis'><code>die</code>(<code>_</code>(<code>"bad</code> <code>revision</code> <code>%s"</code>)<code>,</code> <code>revision</code>)</span>.</p>
 </li>
 <li>
 <p>Error messages from the plumbing commands are sometimes meant for
 machine consumption and should not be marked for translation,
-e.g., <code>die("bad revision %s", revision)</code>.</p>
+e.g., <span class='synopsis'><code>die</code>(<code>"bad</code> <code>revision</code> <code>%s",</code> <code>revision</code>)</span>.</p>
 </li>
 <li>
 <p>BUG("message") are for communicating the specific error to developers,
@@ -1189,7 +1190,7 @@
 in the abstract.  E.g.</p>
 <div class="dlist">
 <dl>
-<dt class="hdlist1" id="Documentation/CodingGuidelines-code--shortcode"><a id="Documentation/CodingGuidelines---short" class="anchor" href="#Documentation/CodingGuidelines---short"></a><code>--short</code> </dt>
+<dt class="hdlist1" id="Documentation/CodingGuidelines-spanclasssynopsiscode--shortcodespan"><a id="Documentation/CodingGuidelines---short" class="anchor" href="#Documentation/CodingGuidelines---short"></a><span class='synopsis'><code>--short</code></span> </dt>
 <dd>
 <p>Emit output in the short-format.</p>
 <div class="literalblock">
@@ -1198,19 +1199,19 @@
 </div>
 </div>
 </dd>
-<dt class="hdlist1" id="Documentation/CodingGuidelines-code--shortcode-1"><a id="Documentation/CodingGuidelines---short-1" class="anchor" href="#Documentation/CodingGuidelines---short-1"></a><code>--short</code> </dt>
+<dt class="hdlist1" id="Documentation/CodingGuidelines-spanclasssynopsiscode--shortcodespan-1"><a id="Documentation/CodingGuidelines---short-1" class="anchor" href="#Documentation/CodingGuidelines---short-1"></a><span class='synopsis'><code>--short</code></span> </dt>
 <dd>
 <p>Use this to emit output in the short-format.</p>
 </dd>
-<dt class="hdlist1" id="Documentation/CodingGuidelines-code--shortcode-1-1"><a id="Documentation/CodingGuidelines---short-1-1" class="anchor" href="#Documentation/CodingGuidelines---short-1-1"></a><code>--short</code> </dt>
+<dt class="hdlist1" id="Documentation/CodingGuidelines-spanclasssynopsiscode--shortcodespan-1-1"><a id="Documentation/CodingGuidelines---short-1-1" class="anchor" href="#Documentation/CodingGuidelines---short-1-1"></a><span class='synopsis'><code>--short</code></span> </dt>
 <dd>
 <p>You can use this to get output in the short-format.</p>
 </dd>
-<dt class="hdlist1" id="Documentation/CodingGuidelines-code--shortcode-1-1-1"><a id="Documentation/CodingGuidelines---short-1-1-1" class="anchor" href="#Documentation/CodingGuidelines---short-1-1-1"></a><code>--short</code> </dt>
+<dt class="hdlist1" id="Documentation/CodingGuidelines-spanclasssynopsiscode--shortcodespan-1-1-1"><a id="Documentation/CodingGuidelines---short-1-1-1" class="anchor" href="#Documentation/CodingGuidelines---short-1-1-1"></a><span class='synopsis'><code>--short</code></span> </dt>
 <dd>
 <p>A user who prefers shorter output could&#8230;&#8203;.</p>
 </dd>
-<dt class="hdlist1" id="Documentation/CodingGuidelines-code--shortcode-1-1-1-1"><a id="Documentation/CodingGuidelines---short-1-1-1-1" class="anchor" href="#Documentation/CodingGuidelines---short-1-1-1-1"></a><code>--short</code> </dt>
+<dt class="hdlist1" id="Documentation/CodingGuidelines-spanclasssynopsiscode--shortcodespan-1-1-1-1"><a id="Documentation/CodingGuidelines---short-1-1-1-1" class="anchor" href="#Documentation/CodingGuidelines---short-1-1-1-1"></a><span class='synopsis'><code>--short</code></span> </dt>
 <dd>
 <p>Should a person and/or program want shorter output, he
 she/they/it can&#8230;&#8203;</p>

external/docs/content/docs/CodingGuidelines/2.22.1.html

@@ -673,10 +673,11 @@
 </li>
 <li>
 <p>You can launch gdb around your program using the shorthand GIT_DEBUGGER.
-Run <code>GIT_DEBUGGER=1 ./bin-wrappers/git foo</code> to simply use gdb as is, or
-run <code>GIT_DEBUGGER="&lt;debugger&gt; &lt;debugger-args&gt;" ./bin-wrappers/git foo</code> to
-use your own debugger and arguments. Example: <code>GIT_DEBUGGER="ddd --gdb"
-./bin-wrappers/git log</code> (See <code>wrap-for-bin.sh</code>.)</p>
+Run <span class='synopsis'><code>GIT_DEBUGGER=1</code> <code>./bin-wrappers/git</code> <code>foo</code></span> to simply use gdb as is, or
+run <span class='synopsis'><code>GIT_DEBUGGER="</code><em>&lt;debugger&gt;</em> <em>&lt;debugger-args&gt;</em><code>"</code> <code>./bin-wrappers/git</code> <code>foo</code></span> to
+use your own debugger and arguments. Example: <span class='synopsis'><code>GIT_DEBUGGER="ddd</code> <code>--gdb"</code>
+
+<code>./bin-wrappers/git</code> <code>log</code></span> (See <span class='synopsis'><code>wrap-for-bin.sh</code></span>.)</p>
 </li>
 </ul>
 </div>

external/docs/content/docs/CodingGuidelines/2.25.0.html

@@ -668,10 +668,11 @@
 </li>
 <li>
 <p>You can launch gdb around your program using the shorthand GIT_DEBUGGER.
-Run <code>GIT_DEBUGGER=1 ./bin-wrappers/git foo</code> to simply use gdb as is, or
-run <code>GIT_DEBUGGER="&lt;debugger&gt; &lt;debugger-args&gt;" ./bin-wrappers/git foo</code> to
-use your own debugger and arguments. Example: <code>GIT_DEBUGGER="ddd --gdb"
-./bin-wrappers/git log</code> (See <code>wrap-for-bin.sh</code>.)</p>
+Run <span class='synopsis'><code>GIT_DEBUGGER=1</code> <code>./bin-wrappers/git</code> <code>foo</code></span> to simply use gdb as is, or
+run <span class='synopsis'><code>GIT_DEBUGGER="</code><em>&lt;debugger&gt;</em> <em>&lt;debugger-args&gt;</em><code>"</code> <code>./bin-wrappers/git</code> <code>foo</code></span> to
+use your own debugger and arguments. Example: <span class='synopsis'><code>GIT_DEBUGGER="ddd</code> <code>--gdb"</code>
+
+<code>./bin-wrappers/git</code> <code>log</code></span> (See <span class='synopsis'><code>wrap-for-bin.sh</code></span>.)</p>
 </li>
 </ul>
 </div>

external/docs/content/docs/CodingGuidelines/2.27.0.html

@@ -674,10 +674,11 @@
 </li>
 <li>
 <p>You can launch gdb around your program using the shorthand GIT_DEBUGGER.
-Run <code>GIT_DEBUGGER=1 ./bin-wrappers/git foo</code> to simply use gdb as is, or
-run <code>GIT_DEBUGGER="&lt;debugger&gt; &lt;debugger-args&gt;" ./bin-wrappers/git foo</code> to
-use your own debugger and arguments. Example: <code>GIT_DEBUGGER="ddd --gdb"
-./bin-wrappers/git log</code> (See <code>wrap-for-bin.sh</code>.)</p>
+Run <span class='synopsis'><code>GIT_DEBUGGER=1</code> <code>./bin-wrappers/git</code> <code>foo</code></span> to simply use gdb as is, or
+run <span class='synopsis'><code>GIT_DEBUGGER="</code><em>&lt;debugger&gt;</em> <em>&lt;debugger-args&gt;</em><code>"</code> <code>./bin-wrappers/git</code> <code>foo</code></span> to
+use your own debugger and arguments. Example: <span class='synopsis'><code>GIT_DEBUGGER="ddd</code> <code>--gdb"</code>
+
+<code>./bin-wrappers/git</code> <code>log</code></span> (See <span class='synopsis'><code>wrap-for-bin.sh</code></span>.)</p>
 </li>
 </ul>
 </div>

external/docs/content/docs/CodingGuidelines/2.28.0.html

@@ -697,10 +697,11 @@
 </li>
 <li>
 <p>You can launch gdb around your program using the shorthand GIT_DEBUGGER.
-Run <code>GIT_DEBUGGER=1 ./bin-wrappers/git foo</code> to simply use gdb as is, or
-run <code>GIT_DEBUGGER="&lt;debugger&gt; &lt;debugger-args&gt;" ./bin-wrappers/git foo</code> to
-use your own debugger and arguments. Example: <code>GIT_DEBUGGER="ddd --gdb"
-./bin-wrappers/git log</code> (See <code>wrap-for-bin.sh</code>.)</p>
+Run <span class='synopsis'><code>GIT_DEBUGGER=1</code> <code>./bin-wrappers/git</code> <code>foo</code></span> to simply use gdb as is, or
+run <span class='synopsis'><code>GIT_DEBUGGER="</code><em>&lt;debugger&gt;</em> <em>&lt;debugger-args&gt;</em><code>"</code> <code>./bin-wrappers/git</code> <code>foo</code></span> to
+use your own debugger and arguments. Example: <span class='synopsis'><code>GIT_DEBUGGER="ddd</code> <code>--gdb"</code>
+
+<code>./bin-wrappers/git</code> <code>log</code></span> (See <span class='synopsis'><code>wrap-for-bin.sh</code></span>.)</p>
 </li>
 </ul>
 </div>