Autogenerated HTML docs for v2.51.0-315-gbb697

Author: gitster

BreakingChanges.adoc

@@ -239,6 +239,11 @@ These features will be removed.
 +
 The command will be removed.
 
+* Support for `core.commentString=auto` has been deprecated and will
+  be removed in Git 3.0.
++
+cf. <xmqqa59i45wc.fsf@gitster.g>
+
 == Superseded features that will not be deprecated
 
 Some features have gained newer replacements that aim to improve the design in

BreakingChanges.html

@@ -787,6 +787,13 @@ <h3 id="_removals">Removals</h3>
 <p>The command will be removed.</p>
 </div>
 </li>
+<li>
+<p>Support for <code>core.commentString=auto</code> has been deprecated and will
+be removed in Git 3.0.</p>
+<div class="paragraph">
+<p>cf. &lt;xmqqa59i45wc.fsf@gitster.g&gt;</p>
+</div>
+</li>
 </ul>
 </div>
 </div>
@@ -825,7 +832,7 @@ <h2 id="_superseded_features_that_will_not_be_deprecated">Superseded features th
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-07-14 12:11:05 -0700
+Last updated 2025-09-23 13:59:22 -0700
 </div>
 </div>
 </body>

RelNotes/2.52.0.adoc

@@ -24,6 +24,17 @@ UI, Workflows & Features
    "--format=nul", and learns to report the objects format used in the
    repository.
 
+ * "core.commentChar=auto" that attempts to dynamically pick a
+   suitable comment character is non-workable, as it is too much
+   trouble to support for little benefit, and is marked as deprecated.
+
+ * "git send-email" learned to drive "git imap-send" to store already
+   sent e-mails in an IMAP folder.
+
+ * The "promisor-remote" capability mechanism has been updated to
+   allow the "partialCloneFilter" settings and the "token" value to be
+   communicated from the server side.
+
 
 Performance, Internal Implementation, Development Support etc.
 --------------------------------------------------------------
@@ -63,6 +74,19 @@ Performance, Internal Implementation, Development Support etc.
    singleton variable, which has been updated to pass an instance
    throughout the callchain.
 
+ * CodingGuidelines now spells out how bitfields are to be written.
+
+ * Adjust to the way newer versions of cURL selectivel enables tracing
+   options, so that our tests can continue to work.
+   (merge 1b5a6bfff3 jk/curl-global-trace-components later to maint).
+
+ * The clear_alloc_state() API function was not fully clearing the
+   structure for reuse, but since nobody reuses it, replace it with a
+   variant that frees the structure as well, making the callers simpler.
+
+ * "git range-diff" learned a way to limit the memory consumed by
+   O(N*N) cost matrix.
+
 
 Fixes since v2.51
 -----------------
@@ -177,6 +201,22 @@ including security updates, are included in this release.
    exhaust memory storing them redundantly, which has been corrected.
    (merge 88a2dc68c8 ps/upload-pack-oom-protection later to maint).
 
+ * A corner case bug in "git log -L..." has been corrected.
+   (merge e3106998ff sg/line-log-boundary-fixes later to maint).
+
+ * "git rev-parse --short" and friends failed to disambiguate two
+   objects with object names that share common prefix longer than 32
+   characters, which has been fixed.
+   (merge 8655908b9e jc/longer-disambiguation-fix later to maint).
+
+ * Some among "git add -p" and friends ignored color.diff and/or
+   color.ui configuration variables, which is an old regression, which
+   has been corrected.
+   (merge 1092cd6435 jk/add-i-color later to maint).
+
+ * "git subtree" (in contrib/) did not work correctly when splitting
+   squashed subtrees, which has been improved.
+
  * Other code cleanup, docfix, build fix, etc.
    (merge 823d537fa7 kh/doc-git-log-markup-fix later to maint).
    (merge cf7efa4f33 rj/t6137-cygwin-fix later to maint).
@@ -198,3 +238,7 @@ including security updates, are included in this release.
    (merge c25651aefd ds/midx-write-fixes later to maint).
    (merge 069c15d256 rs/object-name-extend-abbrev-len-update later to maint).
    (merge bf5c224537 mm/worktree-doc-typofix later to maint).
+   (merge 31397bc4f7 kh/doc-fast-import-markup-fix later to maint).
+   (merge ac7096723b jc/doc-includeif-hasconfig-remote-url-fix later to maint).
+   (merge fafc9b08b8 ag/doc-sendmail-gmail-example-update later to maint).
+   (merge a66fc22bf9 rs/get-oid-with-flags-cleanup later to maint).

config.adoc

@@ -114,8 +114,7 @@ whose format and meaning depends on the keyword. Supported keywords
 are:
 
 `gitdir`::
-
-	The data that follows the keyword `gitdir:` is used as a glob
+	The data that follows the keyword `gitdir` and a colon is used as a glob
 	pattern. If the location of the .git directory matches the
 	pattern, the include condition is met.
 +
@@ -148,7 +147,7 @@ refer to linkgit:gitignore[5] for details. For convenience:
 	case-insensitively (e.g. on case-insensitive file systems)
 
 `onbranch`::
-	The data that follows the keyword `onbranch:` is taken to be a
+	The data that follows the keyword `onbranch` and a colon is taken to be a
 	pattern with standard globbing wildcards and two additional
 	ones, `**/` and `/**`, that can match multiple path components.
 	If we are in a worktree where the name of the branch that is
@@ -161,8 +160,8 @@ all branches that begin with `foo/`. This is useful if your branches are
 organized hierarchically and you would like to apply a configuration to
 all the branches in that hierarchy.
 
-`hasconfig:remote.*.url:`::
-	The data that follows this keyword is taken to
+`hasconfig:remote.*.url`::
+	The data that follows this keyword and a colon is taken to
 	be a pattern with standard globbing wildcards and two
 	additional ones, `**/` and `/**`, that can match multiple
 	components. The first time this keyword is seen, the rest of

git-config.html

@@ -1405,7 +1405,7 @@ <h3 id="_conditional_includes">Conditional includes</h3>
 <dl>
 <dt class="hdlist1"><code>gitdir</code></dt>
 <dd>
-<p>The data that follows the keyword <code>gitdir:</code> is used as a glob
+<p>The data that follows the keyword <code>gitdir</code> and a colon is used as a glob
 pattern. If the location of the .git directory matches the
 pattern, the include condition is met.</p>
 <div class="paragraph">
@@ -1450,7 +1450,7 @@ <h3 id="_conditional_includes">Conditional includes</h3>
 </dd>
 <dt class="hdlist1"><code>onbranch</code></dt>
 <dd>
-<p>The data that follows the keyword <code>onbranch:</code> is taken to be a
+<p>The data that follows the keyword <code>onbranch</code> and a colon is taken to be a
 pattern with standard globbing wildcards and two additional
 ones, <code>**/</code> and <code>/**</code>, that can match multiple path components.
 If we are in a worktree where the name of the branch that is
@@ -1464,9 +1464,9 @@ <h3 id="_conditional_includes">Conditional includes</h3>
 all the branches in that hierarchy.</p>
 </div>
 </dd>
-<dt class="hdlist1"><code>hasconfig:remote.*.url:</code></dt>
+<dt class="hdlist1"><code>hasconfig:remote.*.url</code></dt>
 <dd>
-<p>The data that follows this keyword is taken to
+<p>The data that follows this keyword and a colon is taken to
 be a pattern with standard globbing wildcards and two
 additional ones, <code>**/</code> and <code>/**</code>, that can match multiple
 components. The first time this keyword is seen, the rest of
@@ -3622,8 +3622,35 @@ <h3 id="_variables">Variables</h3>
 commented, and removes them after the editor returns
 (default <em>#</em>).</p>
 <div class="paragraph">
-<p>If set to "auto", <code>git-commit</code> would select a character that is not
-the beginning character of any line in existing commit messages.</p>
+<p>If set to "auto", <code>git-commit</code> will select a character that is not
+the beginning character of any line in existing commit messages.
+Support for this value is deprecated and will be removed in Git 3.0
+due to the following limitations:</p>
+</div>
+<div class="openblock">
+<div class="content">
+<div class="ulist">
+<ul>
+<li>
+<p>It is incompatible with adding comments in a commit message
+template. This includes the conflicts comments added to
+the commit message by <code>cherry-pick</code>, <code>merge</code>, <code>rebase</code> and
+<code>revert</code>.</p>
+</li>
+<li>
+<p>It is incompatible with adding comments to the commit message
+in the <code>prepare-commit-msg</code> hook.</p>
+</li>
+<li>
+<p>It is incompatible with the <code>fixup</code> and <code>squash</code> commands when
+rebasing,</p>
+</li>
+<li>
+<p>It is not respected by <code>git</code> <code>notes</code></p>
+</li>
+</ul>
+</div>
+</div>
 </div>
 <div class="paragraph">
 <p>Note that these two variables are aliases of each other, and in modern
@@ -7601,6 +7628,35 @@ <h3 id="_variables">Variables</h3>
 "false", which means the "promisor-remote" capability is not
 advertised.</p>
 </dd>
+<dt class="hdlist1">promisor.sendFields</dt>
+<dd>
+<p>A comma or space separated list of additional remote related
+field names. A server sends these field names and the
+associated field values from its configuration when
+advertising its promisor remotes using the "promisor-remote"
+capability, see <a href="gitprotocol-v2.html">gitprotocol-v2(5)</a>. Currently, only the
+"partialCloneFilter" and "token" field names are supported.</p>
+</dd>
+<dt class="hdlist1"><code>partialCloneFilter</code></dt>
+<dd>
+<p>contains the partial clone filter
+used for the remote.</p>
+</dd>
+<dt class="hdlist1"><code>token</code></dt>
+<dd>
+<p>contains an authentication token for the remote.</p>
+<div class="paragraph">
+<p>When a field name is part of this list and a corresponding
+"remote.foo.&lt;field-name&gt;" config variable is set on the server to a
+non-empty value, then the field name and value are sent when
+advertising the promisor remote "foo".</p>
+</div>
+<div class="paragraph">
+<p>This list has no effect unless the "promisor.advertise" config
+variable is set to "true", and the "name" and "url" fields are always
+advertised regardless of this setting.</p>
+</div>
+</dd>
 <dt class="hdlist1">promisor.acceptFromServer</dt>
 <dd>
 <p>If set to "all", a client will accept all the promisor remotes
@@ -7622,6 +7678,61 @@ <h3 id="_variables">Variables</h3>
 to "fetch" and "clone" requests from the client. Name and URL
 comparisons are case sensitive. See <a href="gitprotocol-v2.html">gitprotocol-v2(5)</a>.</p>
 </dd>
+<dt class="hdlist1">promisor.checkFields</dt>
+<dd>
+<p>A comma or space separated list of additional remote related
+field names. A client checks if the values of these fields
+transmitted by a server correspond to the values of these
+fields in its own configuration before accepting a promisor
+remote. Currently, "partialCloneFilter" and "token" are the
+only supported field names.</p>
+<div class="paragraph">
+<p>If one of these field names (e.g., "token") is being checked for an
+advertised promisor remote (e.g., "foo"), three conditions must be met
+for the check of this specific field to pass:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>The corresponding local configuration (e.g., <code>remote.foo.token</code>)
+must be set.</p>
+</li>
+<li>
+<p>The server must advertise the "token" field for remote "foo".</p>
+</li>
+<li>
+<p>The value of the locally configured <code>remote.foo.token</code> must exactly
+match the value advertised by the server for the "token" field.</p>
+<div class="paragraph">
+<p>If any of these conditions is not met for any field name listed in
+<code>promisor.checkFields</code>, the advertised remote "foo" is rejected.</p>
+</div>
+<div class="paragraph">
+<p>For the "partialCloneFilter" field, this allows the client to ensure
+that the server&#8217;s filter matches what it expects locally, preventing
+inconsistencies in filtering behavior. For the "token" field, this can
+be used to verify that authentication credentials match expected
+values.</p>
+</div>
+<div class="paragraph">
+<p>Field values are compared case-sensitively.</p>
+</div>
+<div class="paragraph">
+<p>The "name" and "url" fields are always checked according to the
+<code>promisor.acceptFromServer</code> policy, independently of this setting.</p>
+</div>
+<div class="paragraph">
+<p>The field names and values should be passed by the server through the
+"promisor-remote" capability by using the <code>promisor.sendFields</code> config
+variable. The fields are checked only if the
+<code>promisor.acceptFromServer</code> config variable is not set to "None". If
+set to "None", this config variable has no effect. See
+<a href="gitprotocol-v2.html">gitprotocol-v2(5)</a>.</p>
+</div>
+</li>
+</ol>
+</div>
+</dd>
 <dt class="hdlist1">protocol.allow</dt>
 <dd>
 <p>If set, provide a user defined default policy for all protocols which
@@ -8705,6 +8816,8 @@ <h3 id="_variables">Variables</h3>
 <dt class="hdlist1">sendemail.smtpServerPort</dt>
 <dt class="hdlist1">sendemail.smtpServerOption</dt>
 <dt class="hdlist1">sendemail.smtpUser</dt>
+<dt class="hdlist1">sendemail.imapSentFolder</dt>
+<dt class="hdlist1">sendemail.useImapOnly</dt>
 <dt class="hdlist1">sendemail.thread</dt>
 <dt class="hdlist1">sendemail.transferEncoding</dt>
 <dt class="hdlist1">sendemail.validate</dt>

git-fast-import.adoc

@@ -61,10 +61,10 @@ OPTIONS
 	currently impacts only the `export-marks`, `import-marks`, and
 	`import-marks-if-exists` feature commands.
 +
-	Only enable this option if you trust the program generating the
-	fast-import stream! This option is enabled automatically for
-	remote-helpers that use the `import` capability, as they are
-	already trusted to run their own code.
+Only enable this option if you trust the program generating the
+fast-import stream! This option is enabled automatically for
+remote-helpers that use the `import` capability, as they are
+already trusted to run their own code.
 
 Options for Frontends
 ~~~~~~~~~~~~~~~~~~~~~

git-fast-import.html

@@ -516,13 +516,11 @@ <h2 id="_options">OPTIONS</h2>
 allowed by providing this option on the command line.  This
 currently impacts only the <code>export-marks</code>, <code>import-marks</code>, and
 <code>import-marks-if-exists</code> feature commands.</p>
-<div class="literalblock">
-<div class="content">
-<pre>Only enable this option if you trust the program generating the
+<div class="paragraph">
+<p>Only enable this option if you trust the program generating the
 fast-import stream! This option is enabled automatically for
-remote-helpers that use the `import` capability, as they are
-already trusted to run their own code.</pre>
-</div>
+remote-helpers that use the <code>import</code> capability, as they are
+already trusted to run their own code.</p>
 </div>
 </dd>
 </dl>
@@ -2609,7 +2607,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-09-12 12:13:52 -0700
+Last updated 2025-09-23 13:59:22 -0700
 </div>
 </div>
 </body>