Autogenerated HTML docs for v2.49.0-411-ga2955

Author: gitster

MyFirstContribution.html

@@ -999,9 +999,9 @@ <h3 id="implementation"><a class="anchor" href="#implementation"></a>Implementat
 </div>
 </div>
 <div class="paragraph">
-<p>The <code>struct</code> <code>strbuf</code> provides some safety belts to your basic <code>char</code>*, one of
+<p>The <code>struct</code> <code>strbuf</code> provides some safety belts to your basic <code>char*</code>, one of
 which is a length member to prevent buffer overruns. It needs to be initialized
-nicely with <code>STRBUF_INIT</code>. Keep it in mind when you need to pass around <code>char</code>*.</p>
+nicely with <code>STRBUF_INIT</code>. Keep it in mind when you need to pass around <code>char*</code>.</p>
 </div>
 <div class="paragraph">
 <p><code>lookup_commit_reference_by_name</code> resolves the name you pass it, so you can play
@@ -1041,7 +1041,7 @@ <h3 id="add-documentation"><a class="anchor" href="#add-documentation"></a>Addin
 <p>Your new command is undocumented! Let&#8217;s fix that.</p>
 </div>
 <div class="paragraph">
-<p>Take a look at <code>Documentation/git-</code>*.<code>adoc</code>. These are the manpages for the
+<p>Take a look at <code>Documentation/git-*.adoc</code>. These are the manpages for the
 subcommands that Git knows about. You can open these up and take a look to get
 acquainted with the format, but then go ahead and make a new file
 <code>Documentation/git-psuh.adoc</code>. Like with most of the documentation in the Git
@@ -1897,7 +1897,7 @@ <h3 id="sending-git-send-email"><a class="anchor" href="#sending-git-send-email"
 <td class="content">
 If you&#8217;re not sure whom to CC, running <code>contrib/contacts/git-contacts</code> can
 list potential reviewers. In addition, you can do <code>git</code> <code>send-email</code>
-<code>--cc-cmd=</code>'perl <code>contrib/contacts/git-contacts</code>' <code>feature/</code>*.<code>patch</code><sup class="footnote" id="_footnote_contrib-scripts">[<a id="_footnoteref_1" class="footnote" href="#_footnotedef_1" title="View footnote.">1</a>]</sup> to
+<code>--cc-cmd=</code>'perl <code>contrib/contacts/git-contacts</code>' <code>feature/*.patch</code><sup class="footnote" id="_footnote_contrib-scripts">[<a id="_footnoteref_1" class="footnote" href="#_footnotedef_1" title="View footnote.">1</a>]</sup> to
 automatically pass this list of emails to <code>send-email</code>.
 </td>
 </tr>
@@ -1973,7 +1973,7 @@ <h3 id="v2-git-send-email"><a class="anchor" href="#v2-git-send-email"></a>Sendi
 directory, alongside the v1 patches. Using a single directory makes it easy to
 refer to the old v1 patches while proofreading the v2 patches, but you will need
 to be careful to send out only the v2 patches. We will use a pattern like
-<code>psuh/v2-</code>*.<code>patch</code> (not <code>psuh/</code>*.<code>patch</code>, which would match v1 and v2 patches).</p>
+<code>psuh/v2-*.patch</code> (not <code>psuh/*.patch</code>, which would match v1 and v2 patches).</p>
 </div>
 <div class="paragraph">
 <p>Edit your cover letter again. Now is a good time to mention what&#8217;s different
@@ -2239,7 +2239,7 @@ <h3 id="after-approval"><a class="anchor" href="#after-approval"></a>After Revie
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-03-10 09:41:59 -0700
+Last updated 2025-03-26 00:41:02 -0700
 </div>
 </div>
 </body>

MyFirstObjectWalk.html

@@ -956,7 +956,7 @@ <h4 id="_performing_the_walk">Performing the Walk!</h4>
 <div class="title">Note</div>
 </td>
 <td class="content">
-<code>puts</code>() prints a <code>char</code>* to <code>stdout</code>. Since this is the part of the
+<code>puts</code>() prints a <code>char*</code> to <code>stdout</code>. Since this is the part of the
 command we expect to be machine-parsed, we&#8217;re sending it directly to stdout.
 </td>
 </tr>
@@ -1184,7 +1184,7 @@ <h2 id="_basic_object_walk">Basic Object Walk</h2>
 <div class="ulist">
 <ul>
 <li>
-<p><code>struct</code> <code>rev_info</code> *revs: This is the <code>rev_info</code> used for the walk. If
+<p><code>struct</code> <code>rev_info</code> <code>*revs</code>: This is the <code>rev_info</code> used for the walk. If
 its <code>filter</code> member is not <code>NULL</code>, then <code>filter</code> contains information for
 how to filter the object list.</p>
 </li>
@@ -1197,7 +1197,7 @@ <h2 id="_basic_object_walk">Basic Object Walk</h2>
 non-commit object (so each blob, tree, or tag).</p>
 </li>
 <li>
-<p><code>void</code> *show_data: A context buffer which is passed in turn to <code>show_commit</code>
+<p><code>void</code> <code>*show_data</code>: A context buffer which is passed in turn to <code>show_commit</code>
 and <code>show_object</code>.</p>
 </li>
 </ul>
@@ -1208,7 +1208,7 @@ <h2 id="_basic_object_walk">Basic Object Walk</h2>
 <div class="ulist">
 <ul>
 <li>
-<p><code>struct</code> <code>oidset</code> *omitted: A linked-list of object IDs which the provided
+<p><code>struct</code> <code>oidset</code> <code>*omitted</code>: A linked-list of object IDs which the provided
 filter caused to be omitted.</p>
 </li>
 </ul>
@@ -1675,7 +1675,7 @@ <h2 id="_wrapping_up">Wrapping Up</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-03-10 09:41:59 -0700
+Last updated 2025-03-26 00:41:02 -0700
 </div>
 </div>
 </body>

RelNotes/2.50.0.adoc

@@ -110,6 +110,8 @@ Performance, Internal Implementation, Development Support etc.
  * Remove remnants of the recursive merge strategy backend, which was
    superseded by the ort merge strategy.
 
+ * Optimize the code to dedup references recorded in a bundle file.
+
 
 Fixes since v2.49
 -----------------
@@ -195,6 +197,19 @@ Fixes since v2.49
  * Incorrect sorting of refs with bytes with high-bit set on platforms
    with signed char led to a BUG, which has been corrected.
 
+ * "make perf" fixes.
+   (merge 1665f12fa0 pb/perf-test-fixes later to maint).
+
+ * Doc mark-up updates.
+   (merge 5a5565ec44 ja/doc-reset-mv-rm-markup-updates later to maint).
+
+ * Work around false positive from CodeQL checker.
+   (merge 0f558141ed js/range-check-codeql-workaround later to maint).
+
+ * "git log --{left,right}-only A...B", when A and B does not share
+   any common ancestor, now behaves as expected.
+   (merge e7ef4be7c2 mh/left-right-limited later to maint).
+
  * Other code cleanup, docfix, build fix, etc.
    (merge 227c4f33a0 ja/doc-block-delimiter-markup-fix later to maint).
    (merge 2bfd3b3685 ab/decorate-code-cleanup later to maint).

SubmittingPatches.html

@@ -1552,11 +1552,11 @@ <h3 id="_thunderbird_kmail_gmail">Thunderbird, KMail, GMail</h3>
 <div class="sect2">
 <h3 id="_gnus">Gnus</h3>
 <div class="paragraph">
-<p>"|" in the *Summary* buffer can be used to pipe the current
+<p>"|" in the <code>*Summary*</code> buffer can be used to pipe the current
 message to an external program, and this is a handy way to drive
 <code>git</code> <code>am</code>.  However, if the message is MIME encoded, what is
 piped into the program is the representation you see in your
-*Article* buffer after unwrapping MIME.  This is often not what
+<code>*Article*</code> buffer after unwrapping MIME.  This is often not what
 you would want for two reasons.  It tends to screw up non-ASCII
 characters (most notably in people&#8217;s names), and also
 whitespaces (fatal in patches).  Running "C-u g" to display the

git-add.html

@@ -509,7 +509,7 @@ <h2 id="_options">OPTIONS</h2>
 <dl>
 <dt class="hdlist1"><em>&lt;pathspec&gt;</em>...</dt>
 <dd>
-<p>Files to add content from.  Fileglobs (e.g. *.<code>c</code>) can
+<p>Files to add content from.  Fileglobs (e.g. <code>*.c</code>) can
 be given to add all matching files.  Also a
 leading directory name (e.g. <code>dir</code> to add <code>dir/file1</code>
 and <code>dir/file2</code>) can be given to update the index to
@@ -709,21 +709,21 @@ <h2 id="_examples">EXAMPLES</h2>
 <div class="ulist">
 <ul>
 <li>
-<p>Adds content from all *.<code>txt</code> files under <code>Documentation</code> directory
+<p>Adds content from all <code>*.txt</code> files under <code>Documentation</code> directory
 and its subdirectories:</p>
 <div class="listingblock">
 <div class="content">
 <pre>$ git add Documentation/\*.txt</pre>
 </div>
 </div>
 <div class="paragraph">
-<p>Note that the asterisk * is quoted from the shell in this
+<p>Note that the asterisk <code>*</code> is quoted from the shell in this
 example; this lets the command include the files from
 subdirectories of <code>Documentation/</code> directory.</p>
 </div>
 </li>
 <li>
-<p>Considers adding content from all <code>git-</code>*.<code>sh</code> scripts:</p>
+<p>Considers adding content from all <code>git-*.sh</code> scripts:</p>
 <div class="listingblock">
 <div class="content">
 <pre>$ git add git-*.sh</pre>

git-am.html

@@ -832,7 +832,7 @@ <h2 id="_configuration">CONFIGURATION</h2>
 <dd>
 <p>If true, git-am will call git-mailsplit for patches in mbox format
 with parameter <code>--keep-cr</code>. In this case git-mailsplit will
-not remove \r from lines ending with \r\n. Can be overridden
+not remove <code>\r</code> from lines ending with <code>\r\n</code>. Can be overridden
 by giving <code>--no-keep-cr</code> from the command line.
 See <a href="git-am.html">git-am(1)</a>, <a href="git-mailsplit.html">git-mailsplit(1)</a>.</p>
 </dd>

git-check-ref-format.html

@@ -491,15 +491,15 @@ <h2 id="_description">DESCRIPTION</h2>
 is waived.</p>
 </li>
 <li>
-<p>They cannot have two consecutive dots .. anywhere.</p>
+<p>They cannot have two consecutive dots <code>..</code> anywhere.</p>
 </li>
 <li>
 <p>They cannot have ASCII control characters (i.e. bytes whose
 values are lower than \040, or \177 <code>DEL</code>), space, tilde <code>~</code>,
 caret <code>^</code>, or colon <code>:</code> anywhere.</p>
 </li>
 <li>
-<p>They cannot have question-mark ?, asterisk *, or open
+<p>They cannot have question-mark ?, asterisk <code>*</code>, or open
 bracket [ anywhere.  See the <code>--refspec-pattern</code> option below for
 an exception to this rule.</p>
 </li>
@@ -518,7 +518,7 @@ <h2 id="_description">DESCRIPTION</h2>
 <p>They cannot be the single character <code>@</code>.</p>
 </li>
 <li>
-<p>They cannot contain a \.</p>
+<p>They cannot contain a <code>\</code>.</p>
 </li>
 </ol>
 </div>
@@ -531,7 +531,7 @@ <h2 id="_description">DESCRIPTION</h2>
 <div class="olist arabic">
 <ol class="arabic">
 <li>
-<p>A double-dot .. is often used as in <code>ref1</code><code>..</code><code>ref2</code>, and in some
+<p>A double-dot <code>..</code> is often used as in <code>ref1</code><code>..</code><code>ref2</code>, and in some
 contexts this notation means <code>^ref1</code> <code>ref2</code> (i.e. not in
 <code>ref1</code> and in <code>ref2</code>).</p>
 </li>
@@ -587,9 +587,9 @@ <h2 id="_options">OPTIONS</h2>
 <dd>
 <p>Interpret &lt;refname&gt; as a reference name pattern for a refspec
 (as used with remote repositories).  If this option is
-enabled, &lt;refname&gt; is allowed to contain a single *
-in the refspec (e.g., <code>foo/bar</code>*/baz or <code>foo/bar</code>*baz/
-but not <code>foo/bar</code>*/baz*).</p>
+enabled, &lt;refname&gt; is allowed to contain a single <code>*</code>
+in the refspec (e.g., <code>foo/bar*/baz</code> or <code>foo/bar*baz/</code>
+but not <code>foo/bar*/baz*</code>).</p>
 </dd>
 <dt class="hdlist1">--normalize</dt>
 <dd>

git-checkout-index.html

@@ -562,7 +562,7 @@ <h2 id="_options">OPTIONS</h2>
 </div>
 </div>
 <div class="paragraph">
-<p>which will force all existing *.<code>h</code> files to be replaced with their
+<p>which will force all existing <code>*.h</code> files to be replaced with their
 cached copies. If an empty command line implied "all", then this would
 force-refresh everything in the index, which was not the point.  But
 since <em>git checkout-index</em> accepts --stdin it would be faster to use:</p>

git-checkout.html

@@ -1112,7 +1112,7 @@ <h3 id="_1_paths">1. Paths</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Note the quotes around *.<code>c</code>.  The file <code>hello.c</code> will also be
+<p>Note the quotes around <code>*.c</code>.  The file <code>hello.c</code> will also be
 checked out, even though it is no longer in the working tree,
 because the file globbing is used to match entries in the index
 (not in the working tree by the shell).</p>

git-clone.html

@@ -863,7 +863,7 @@ <h2 id="_options">OPTIONS</h2>
 <dd>
 <p>Before fetching from the remote, fetch a bundle from the given
 <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>*
+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>.</p>
 </dd>

git-commit.html

@@ -705,11 +705,11 @@ <h2 id="_options">OPTIONS</h2>
 <dt class="hdlist1"><code>--trailer</code> <em>&lt;token&gt;</em>[(<code>=</code>|<code>:</code>)<em>&lt;value&gt;</em>]</dt>
 <dd>
 <p>Specify a (<em>&lt;token&gt;</em>, <em>&lt;value&gt;</em>) pair that should be applied as a
-trailer. (e.g. <code>git</code> <code>commit</code> <code>--trailer</code> "Signed-off-by:C <code>O</code> <code>Mitter</code> \
-&lt;committer@example.<code>com</code>&gt;" <code>--trailer</code> "Helped-by:C <code>O</code> <code>Mitter</code> \
+trailer. (e.g. <code>git</code> <code>commit</code> <code>--trailer</code> "Signed-off-by:C <code>O</code> <code>Mitter</code> <code>\</code>
+&lt;committer@example.<code>com</code>&gt;" <code>--trailer</code> "Helped-by:C <code>O</code> <code>Mitter</code> <code>\</code>
 &lt;committer@example.<code>com</code>&gt;" will add the <code>Signed-off-by</code> trailer
 and the <code>Helped-by</code> trailer to the commit message.)
-The <code>trailer.</code>* configuration variables
+The <code>trailer.*</code> configuration variables
 (<a href="git-interpret-trailers.html">git-interpret-trailers(1)</a>) can be used to define if
 a duplicated trailer is omitted, where in the run of trailers
 each trailer would appear, and other details.</p>