Autogenerated HTML docs for v2.52.0-rc0-28-g4cf91

Author: gitster

MyFirstContribution.adoc

@@ -1153,6 +1153,11 @@ NOTE: When you are sending a real patch, it will go to [email protected] - but
 please don't send your patchset from the tutorial to the real mailing list! For
 now, you can send it to yourself, to make sure you understand how it will look.
 
+NOTE: After sending your patches, you can confirm that they reached the mailing
+list by visiting https://lore.kernel.org/git/. Use the search bar to find your
+name or the subject of your patch. If it appears, your email was successfully
+delivered.
+
 After you run the command above, you will be presented with an interactive
 prompt for each patch that's about to go out. This gives you one last chance to
 edit or quit sending something (but again, don't edit code this way). Once you

MyFirstContribution.html

@@ -1951,6 +1951,21 @@ <h3 id="sending-git-send-email"><a class="anchor" href="#sending-git-send-email"
 </tr>
 </table>
 </div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<div class="title">Note</div>
+</td>
+<td class="content">
+After sending your patches, you can confirm that they reached the mailing
+list by visiting <a href="https://lore.kernel.org/git/" class="bare">https://lore.kernel.org/git/</a>. Use the search bar to find your
+name or the subject of your patch. If it appears, your email was successfully
+delivered.
+</td>
+</tr>
+</table>
+</div>
 <div class="paragraph">
 <p>After you run the command above, you will be presented with an interactive
 prompt for each patch that&#8217;s about to go out. This gives you one last chance to
@@ -2273,7 +2288,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-09-02 11:08:10 -0700
+Last updated 2025-11-04 11:37:22 -0800
 </div>
 </div>
 </body>

RelNotes/2.52.0.adoc

@@ -74,6 +74,8 @@ UI, Workflows & Features
    avoids doing maintenance tasks that rebuilds everything from
    scratch.
 
+ * "git repo structure", a new command.
+
 
 Performance, Internal Implementation, Development Support etc.
 --------------------------------------------------------------
@@ -165,6 +167,18 @@ Performance, Internal Implementation, Development Support etc.
  * The code to walk revision graph to compute merge base has been
    optimized.
 
+ * AI guidelines has been added to our documentation set.
+
+ * Contributed credential helpers (obviously in contrib/) now have "cd
+   $there && make install" target.
+
+ * The "MyFirstContribution" tutorial tells the reader how to send out
+   their patches; the section gained a hint to verify the message
+   reached the mailing list.
+
+ * The "debug" ref-backend was missing a method implementation, which
+   has been corrected.
+
 
 Fixes since v2.51
 -----------------
@@ -397,6 +411,15 @@ including security updates, are included in this release.
    "foo**/bar" match with "foobar", which has been corrected.
    (merge 1940a02dc1 jk/match-pathname-fix later to maint).
 
+ * Tests did not set up GNUPGHOME correctly, which is fixed but some
+   flaky tests are exposed in t1016, which needs to be addressed
+   before this topic can move forward.
+   (merge 6cd8369ef3 tz/test-prepare-gnupghome later to maint).
+
+ * The patterns used in the .gitignore files use backslash in the way
+   documented for fnmatch(3); document as such to reduce confusion.
+   (merge 8a6d158a1d jk/doc-backslash-in-exclude later to maint).
+
  * Other code cleanup, docfix, build fix, etc.
    (merge 529a60a885 ua/t1517-short-help-tests later to maint).
    (merge 22d421fed9 ac/deglobal-fmt-merge-log-config later to maint).
@@ -409,3 +432,5 @@ including security updates, are included in this release.
    (merge 15b8abde07 js/mingw-includes-cleanup later to maint).
    (merge 2cebca0582 tb/cat-file-objectmode-update later to maint).
    (merge 8f487db07a kh/doc-patch-id-1 later to maint).
+   (merge f711f37b05 eb/t1016-hash-transition-fix later to maint).
+   (merge 85333aa1af jk/test-delete-gpgsig-leakfix later to maint).

SubmittingPatches.adoc

@@ -446,6 +446,34 @@ highlighted above.
 Only capitalize the very first letter of the trailer, i.e. favor
 "Signed-off-by" over "Signed-Off-By" and "Acked-by:" over "Acked-By".
 
+[[ai]]
+=== Use of Artificial Intelligence (AI)
+
+The Developer's Certificate of Origin requires contributors to certify
+that they know the origin of their contributions to the project and
+that they have the right to submit it under the project's license.
+It's not yet clear that this can be legally satisfied when submitting
+significant amount of content that has been generated by AI tools.
+
+Another issue with AI generated content is that AIs still often
+hallucinate or just produce bad code, commit messages, documentation
+or output, even when you point out their mistakes.
+
+To avoid these issues, we will reject anything that looks AI
+generated, that sounds overly formal or bloated, that looks like AI
+slop, that looks good on the surface but makes no sense, or that
+senders don’t understand or cannot explain.
+
+We strongly recommend using AI tools carefully and responsibly.
+
+Contributors would often benefit more from AI by using it to guide and
+help them step by step towards producing a solution by themselves
+rather than by asking for a full solution that they would then mostly
+copy-paste. They can also use AI to help with debugging, or with
+checking for obvious mistakes, things that can be improved, things
+that don’t match our style, guidelines or our feedback, before sending
+it to us.
+
 [[git-tools]]
 === Generate your patch using Git tools out of your commits.
 

SubmittingPatches.html

@@ -1023,6 +1023,39 @@ <h3 id="sign-off">Certify your work by adding your <code>Signed-off-by</code> tr
 </div>
 </div>
 <div class="sect2">
+<h3 id="ai">Use of Artificial Intelligence (AI)</h3>
+<div class="paragraph">
+<p>The Developer&#8217;s Certificate of Origin requires contributors to certify
+that they know the origin of their contributions to the project and
+that they have the right to submit it under the project&#8217;s license.
+It&#8217;s not yet clear that this can be legally satisfied when submitting
+significant amount of content that has been generated by AI tools.</p>
+</div>
+<div class="paragraph">
+<p>Another issue with AI generated content is that AIs still often
+hallucinate or just produce bad code, commit messages, documentation
+or output, even when you point out their mistakes.</p>
+</div>
+<div class="paragraph">
+<p>To avoid these issues, we will reject anything that looks AI
+generated, that sounds overly formal or bloated, that looks like AI
+slop, that looks good on the surface but makes no sense, or that
+senders don’t understand or cannot explain.</p>
+</div>
+<div class="paragraph">
+<p>We strongly recommend using AI tools carefully and responsibly.</p>
+</div>
+<div class="paragraph">
+<p>Contributors would often benefit more from AI by using it to guide and
+help them step by step towards producing a solution by themselves
+rather than by asking for a full solution that they would then mostly
+copy-paste. They can also use AI to help with debugging, or with
+checking for obvious mistakes, things that can be improved, things
+that don’t match our style, guidelines or our feedback, before sending
+it to us.</p>
+</div>
+</div>
+<div class="sect2">
 <h3 id="git-tools">Generate your patch using Git tools out of your commits.</h3>
 <div class="paragraph">
 <p>Git based diff tools generate unidiff which is the preferred format.</p>
@@ -1605,7 +1638,7 @@ <h3 id="_gnus">Gnus</h3>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-11-03 07:28:57 -0800
+Last updated 2025-11-04 11:37:22 -0800
 </div>
 </div>
 </body>

git-checkout.adoc

@@ -61,7 +61,7 @@ uncommitted changes.
 `git checkout -B <branch> [<start-point>]`::
 
 	The same as `-b`, except that if the branch already exists it
-	resets `_<branch>_` to the start point instead of failing.
+	resets _<branch>_ to the start point instead of failing.
 
 `git checkout --detach [<branch>]`::
 `git checkout [--detach] <commit>`::
@@ -155,7 +155,7 @@ of it").
 
 `-B <new-branch>`::
 	The same as `-b`, except that if the branch already exists it
-	resets `_<branch>_` to the start point instead of failing.
+	resets _<branch>_ to the start point instead of failing.
 
 `-t`::
 `--track[=(direct|inherit)]`::

git-checkout.html

@@ -523,7 +523,7 @@ <h2 id="_description">DESCRIPTION</h2>
 <dt class="hdlist1"><code>git</code> <code>checkout</code> <code>-B</code> <em>&lt;branch&gt;</em> [<em>&lt;start-point&gt;</em>]</dt>
 <dd>
 <p>The same as <code>-b</code>, except that if the branch already exists it
-resets <code>_</code><em>&lt;branch&gt;</em><code>_</code> to the start point instead of failing.</p>
+resets <em>&lt;branch&gt;</em> to the start point instead of failing.</p>
 </dd>
 <dt class="hdlist1"><code>git</code> <code>checkout</code> <code>--detach</code> [<em>&lt;branch&gt;</em>]</dt>
 <dt class="hdlist1"><code>git</code> <code>checkout</code> [<code>--detach</code>] <em>&lt;commit&gt;</em></dt>
@@ -638,7 +638,7 @@ <h2 id="_options">OPTIONS</h2>
 <dt class="hdlist1"><code>-B</code> <em>&lt;new-branch&gt;</em></dt>
 <dd>
 <p>The same as <code>-b</code>, except that if the branch already exists it
-resets <code>_</code><em>&lt;branch&gt;</em><code>_</code> to the start point instead of failing.</p>
+resets <em>&lt;branch&gt;</em> to the start point instead of failing.</p>
 </dd>
 <dt class="hdlist1"><code>-t</code></dt>
 <dt class="hdlist1"><code>--track</code>[<code>=</code>(<code>direct</code>|<code>inherit</code>)]</dt>
@@ -1311,7 +1311,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-09-29 13:02:52 -0700
+Last updated 2025-11-04 11:37:22 -0800
 </div>
 </div>
 </body>

git-repo.adoc

@@ -9,6 +9,7 @@ SYNOPSIS
 --------
 [synopsis]
 git repo info [--format=(keyvalue|nul)] [-z] [<key>...]
+git repo structure [--format=(table|keyvalue|nul)]
 
 DESCRIPTION
 -----------
@@ -43,6 +44,35 @@ supported:
 +
 `-z` is an alias for `--format=nul`.
 
+`structure [--format=(table|keyvalue|nul)]`::
+	Retrieve statistics about the current repository structure. The
+	following kinds of information are reported:
++
+* Reference counts categorized by type
+* Reachable object counts categorized by type
+
++
+The output format can be chosen through the flag `--format`. Three formats are
+supported:
++
+`table`:::
+	Outputs repository stats in a human-friendly table. This format may
+	change and is not intended for machine parsing. This is the default
+	format.
+
+`keyvalue`:::
+	Each line of output contains a key-value pair for a repository stat.
+	The '=' character is used to delimit between the key and the value.
+	Values containing "unusual" characters are quoted as explained for the
+	configuration variable `core.quotePath` (see linkgit:git-config[1]).
+
+`nul`:::
+	Similar to `keyvalue`, but uses a NUL character to delimit between
+	key-value pairs instead of a newline. Also uses a newline character as
+	the delimiter between the key and value instead of '='. Unlike the
+	`keyvalue` format, values containing "unusual" characters are never
+	quoted.
+
 INFO KEYS
 ---------
 In order to obtain a set of values from `git repo info`, you should provide

git-repo.html

@@ -452,7 +452,8 @@ <h2 id="_name">NAME</h2>
 <h2 id="_synopsis">SYNOPSIS</h2>
 <div class="sectionbody">
 <div class="verseblock">
-<pre class="content"><code>git</code> <code>repo</code> <code>info</code> [<code>--format=</code>(<code>keyvalue</code>|<code>nul</code>)] [<code>-z</code>] [<em>&lt;key&gt;</em>&#8230;&#8203;]</pre>
+<pre class="content"><code>git</code> <code>repo</code> <code>info</code> [<code>--format=</code>(<code>keyvalue</code>|<code>nul</code>)] [<code>-z</code>] [<em>&lt;key&gt;</em>&#8230;&#8203;]
+<code>git</code> <code>repo</code> <code>structure</code> [<code>--format=</code>(<code>table</code>|<code>keyvalue</code>|<code>nul</code>)]</pre>
 </div>
 </div>
 </div>
@@ -507,6 +508,53 @@ <h2 id="_commands">COMMANDS</h2>
 </dl>
 </div>
 </dd>
+<dt class="hdlist1"><code>structure</code> [<code>--format=</code>(<code>table</code>|<code>keyvalue</code>|<code>nul</code>)]</dt>
+<dd>
+<p>Retrieve statistics about the current repository structure. The
+following kinds of information are reported:</p>
+<div class="ulist">
+<ul>
+<li>
+<p>Reference counts categorized by type</p>
+</li>
+<li>
+<p>Reachable object counts categorized by type</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>The output format can be chosen through the flag <code>--format</code>. Three formats are
+supported:</p>
+</div>
+<div class="paragraph">
+<p>+</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1"><code>table</code></dt>
+<dd>
+<p>Outputs repository stats in a human-friendly table. This format may
+change and is not intended for machine parsing. This is the default
+format.</p>
+</dd>
+<dt class="hdlist1"><code>keyvalue</code></dt>
+<dd>
+<p>Each line of output contains a key-value pair for a repository stat.
+The <em>=</em> character is used to delimit between the key and the value.
+Values containing "unusual" characters are quoted as explained for the
+configuration variable <code>core.quotePath</code> (see <a href="git-config.html">git-config(1)</a>).</p>
+</dd>
+<dt class="hdlist1"><code>nul</code></dt>
+<dd>
+<p>Similar to <code>keyvalue</code>, but uses a NUL character to delimit between
+key-value pairs instead of a newline. Also uses a newline character as
+the delimiter between the key and value instead of <em>=</em>. Unlike the
+<code>keyvalue</code> format, values containing "unusual" characters are never
+quoted.</p>
+</dd>
+</dl>
+</div>
+</dd>
 </dl>
 </div>
 </div>
@@ -597,7 +645,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-09-15 10:47:08 -0700
+Last updated 2025-11-04 11:37:22 -0800
 </div>
 </div>
 </body>

gitignore.adoc

@@ -111,6 +111,11 @@ PATTERN FORMAT
    one of the characters in a range. See fnmatch(3) and the
    FNM_PATHNAME flag for a more detailed description.
 
+ - A backslash ("`\`") can be used to escape any character. E.g., "`\*`"
+   matches a literal asterisk (and "`\a`" matches "`a`", even though
+   there is no need for escaping there). As with fnmatch(3), a backslash
+   at the end of a pattern is an invalid pattern that never matches.
+
 Two consecutive asterisks ("`**`") in patterns matched against
 full pathname may have special meaning: