Autogenerated HTML docs for v2.52.0-rc0

Author: gitster

RelNotes/2.52.0.adoc

@@ -70,6 +70,10 @@ UI, Workflows & Features
  * "Symlink symref" has been added to the list of things that will
    disappear at Git 3.0 boundary.
 
+ * "git maintenance" command learns the "geometric" strategy where it
+   avoids doing maintenance tasks that rebuilds everything from
+   scratch.
+
 
 Performance, Internal Implementation, Development Support etc.
 --------------------------------------------------------------
@@ -158,6 +162,9 @@ Performance, Internal Implementation, Development Support etc.
  * Two slightly different ways to get at "all the packfiles" in API
    has been cleaned up.
 
+ * The code to walk revision graph to compute merge base has been
+   optimized.
+
 
 Fixes since v2.51
 -----------------
@@ -382,6 +389,14 @@ including security updates, are included in this release.
    and "git bisect unknown", which has been corrected.
    (merge 2bb3a012f3 rz/bisect-help-unknown later to maint).
 
+ * The 'q'(uit) command in "git add -p" has been improved to quit
+   without doing any meaningless work before leaving, and giving EOF
+   (typically control-D) to the prompt is made to behave the same way.
+
+ * The wildmatch code had a corner case bug that mistakenly makes
+   "foo**/bar" match with "foobar", which has been corrected.
+   (merge 1940a02dc1 jk/match-pathname-fix 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).
@@ -393,3 +408,4 @@ including security updates, are included in this release.
    (merge a66fc22bf9 rs/get-oid-with-flags-cleanup later to maint).
    (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).

SubmittingPatches.html

@@ -1605,7 +1605,7 @@ <h3 id="_gnus">Gnus</h3>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-10-20 13:23:01 -0700
+Last updated 2025-11-03 07:28:57 -0800
 </div>
 </div>
 </body>

git-config.html

@@ -6708,23 +6708,47 @@ <h3 id="_variables">Variables</h3>
 <dt class="hdlist1">maintenance.strategy</dt>
 <dd>
 <p>This string config option provides a way to specify one of a few
-recommended schedules for background maintenance. This only affects
-which tasks are run during <code>git</code> <code>maintenance</code> <code>run</code> <code>--schedule=X</code>
-commands, provided no <code>--task=</code><em>&lt;task&gt;</em> arguments are provided.
-Further, if a <code>maintenance.</code><em>&lt;task&gt;</em><code>.schedule</code> config value is set,
-then that value is used instead of the one provided by
-<code>maintenance.strategy</code>. The possible strategy strings are:</p>
+recommended strategies for repository maintenance. This affects
+which tasks are run during <code>git</code> <code>maintenance</code> <code>run</code>, provided no
+<code>--task=</code><em>&lt;task&gt;</em> arguments are provided. This setting impacts manual
+maintenance, auto-maintenance as well as scheduled maintenance. The
+tasks that run may be different depending on the maintenance type.</p>
+<div class="paragraph">
+<p>The maintenance strategy can be further tweaked by setting
+<code>maintenance.</code><em>&lt;task&gt;</em><code>.enabled</code> and <code>maintenance.</code><em>&lt;task&gt;</em><code>.schedule</code>. If set, these
+values are used instead of the defaults provided by <code>maintenance.strategy</code>.</p>
+</div>
+<div class="paragraph">
+<p>The possible strategies are:</p>
+</div>
 <div class="ulist">
 <ul>
 <li>
-<p><code>none</code>: This default setting implies no tasks are run at any schedule.</p>
+<p><code>none</code>: This strategy implies no tasks are run at all. This is the default
+strategy for scheduled maintenance.</p>
+</li>
+<li>
+<p><code>gc</code>: This strategy runs the <code>gc</code> task. This is the default strategy for
+manual maintenance.</p>
+</li>
+<li>
+<p><code>geometric</code>: This strategy performs geometric repacking of packfiles and
+keeps auxiliary data structures up-to-date. The strategy expires data in the
+reflog and removes worktrees that cannot be located anymore. When the
+geometric repacking strategy would decide to do an all-into-one repack, then
+the strategy generates a cruft pack for all unreachable objects. Objects that
+are already part of a cruft pack will be expired.</p>
+<div class="paragraph">
+<p>This repacking strategy is a full replacement for the <code>gc</code> strategy and is
+recommended for large repositories.</p>
+</div>
 </li>
 <li>
 <p><code>incremental</code>: This setting optimizes for performing small maintenance
 activities that do not delete any data. This does not schedule the <code>gc</code>
 task, but runs the <code>prefetch</code> and <code>commit-graph</code> tasks hourly, the
 <code>loose-objects</code> and <code>incremental-repack</code> tasks daily, and the <code>pack-refs</code>
-task weekly.</p>
+task weekly. Manual repository maintenance uses the <code>gc</code> task.</p>
 </li>
 </ul>
 </div>
@@ -6780,6 +6804,24 @@ <h3 id="_variables">Variables</h3>
 number of pack-files not in the multi-pack-index is at least the value
 of <code>maintenance.incremental-repack.auto</code>. The default value is 10.</p>
 </dd>
+<dt class="hdlist1">maintenance.geometric-repack.auto</dt>
+<dd>
+<p>This integer config option controls how often the <code>geometric-repack</code>
+task should be run as part of <code>git</code> <code>maintenance</code> <code>run</code> <code>--auto</code>. If zero,
+then the <code>geometric-repack</code> task will not run with the <code>--auto</code>
+option. A negative value will force the task to run every time.
+Otherwise, a positive value implies the command should run either when
+there are packfiles that need to be merged together to retain the
+geometric progression, or when there are at least this many loose
+objects that would be written into a new packfile. The default value is
+100.</p>
+</dd>
+<dt class="hdlist1">maintenance.geometric-repack.splitFactor</dt>
+<dd>
+<p>This integer config option controls the factor used for the geometric
+sequence. See the <code>--geometric=</code> option in <a href="git-repack.html">git-repack(1)</a> for
+more details. Defaults to <code>2</code>.</p>
+</dd>
 <dt class="hdlist1">maintenance.reflog-expire.auto</dt>
 <dd>
 <p>This integer config option controls how often the <code>reflog-expire</code> task

git-maintenance.html

@@ -1003,23 +1003,47 @@ <h2 id="_configuration">CONFIGURATION</h2>
 <dt class="hdlist1">maintenance.strategy</dt>
 <dd>
 <p>This string config option provides a way to specify one of a few
-recommended schedules for background maintenance. This only affects
-which tasks are run during <code>git</code> <code>maintenance</code> <code>run</code> <code>--schedule=X</code>
-commands, provided no <code>--task=</code><em>&lt;task&gt;</em> arguments are provided.
-Further, if a <code>maintenance.</code><em>&lt;task&gt;</em><code>.schedule</code> config value is set,
-then that value is used instead of the one provided by
-<code>maintenance.strategy</code>. The possible strategy strings are:</p>
+recommended strategies for repository maintenance. This affects
+which tasks are run during <code>git</code> <code>maintenance</code> <code>run</code>, provided no
+<code>--task=</code><em>&lt;task&gt;</em> arguments are provided. This setting impacts manual
+maintenance, auto-maintenance as well as scheduled maintenance. The
+tasks that run may be different depending on the maintenance type.</p>
+<div class="paragraph">
+<p>The maintenance strategy can be further tweaked by setting
+<code>maintenance.</code><em>&lt;task&gt;</em><code>.enabled</code> and <code>maintenance.</code><em>&lt;task&gt;</em><code>.schedule</code>. If set, these
+values are used instead of the defaults provided by <code>maintenance.strategy</code>.</p>
+</div>
+<div class="paragraph">
+<p>The possible strategies are:</p>
+</div>
 <div class="ulist">
 <ul>
 <li>
-<p><code>none</code>: This default setting implies no tasks are run at any schedule.</p>
+<p><code>none</code>: This strategy implies no tasks are run at all. This is the default
+strategy for scheduled maintenance.</p>
+</li>
+<li>
+<p><code>gc</code>: This strategy runs the <code>gc</code> task. This is the default strategy for
+manual maintenance.</p>
+</li>
+<li>
+<p><code>geometric</code>: This strategy performs geometric repacking of packfiles and
+keeps auxiliary data structures up-to-date. The strategy expires data in the
+reflog and removes worktrees that cannot be located anymore. When the
+geometric repacking strategy would decide to do an all-into-one repack, then
+the strategy generates a cruft pack for all unreachable objects. Objects that
+are already part of a cruft pack will be expired.</p>
+<div class="paragraph">
+<p>This repacking strategy is a full replacement for the <code>gc</code> strategy and is
+recommended for large repositories.</p>
+</div>
 </li>
 <li>
 <p><code>incremental</code>: This setting optimizes for performing small maintenance
 activities that do not delete any data. This does not schedule the <code>gc</code>
 task, but runs the <code>prefetch</code> and <code>commit-graph</code> tasks hourly, the
 <code>loose-objects</code> and <code>incremental-repack</code> tasks daily, and the <code>pack-refs</code>
-task weekly.</p>
+task weekly. Manual repository maintenance uses the <code>gc</code> task.</p>
 </li>
 </ul>
 </div>
@@ -1075,6 +1099,24 @@ <h2 id="_configuration">CONFIGURATION</h2>
 number of pack-files not in the multi-pack-index is at least the value
 of <code>maintenance.incremental-repack.auto</code>. The default value is 10.</p>
 </dd>
+<dt class="hdlist1">maintenance.geometric-repack.auto</dt>
+<dd>
+<p>This integer config option controls how often the <code>geometric-repack</code>
+task should be run as part of <code>git</code> <code>maintenance</code> <code>run</code> <code>--auto</code>. If zero,
+then the <code>geometric-repack</code> task will not run with the <code>--auto</code>
+option. A negative value will force the task to run every time.
+Otherwise, a positive value implies the command should run either when
+there are packfiles that need to be merged together to retain the
+geometric progression, or when there are at least this many loose
+objects that would be written into a new packfile. The default value is
+100.</p>
+</dd>
+<dt class="hdlist1">maintenance.geometric-repack.splitFactor</dt>
+<dd>
+<p>This integer config option controls the factor used for the geometric
+sequence. See the <code>--geometric=</code> option in <a href="git-repack.html">git-repack(1)</a> for
+more details. Defaults to <code>2</code>.</p>
+</dd>
 <dt class="hdlist1">maintenance.reflog-expire.auto</dt>
 <dd>
 <p>This integer config option controls how often the <code>reflog-expire</code> task

git-p4.html

@@ -1514,7 +1514,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-06-20 18:10:42 -0700
+Last updated 2025-08-25 14:46:08 -0700
 </div>
 </div>
 </body>

git-pack-refs.html

@@ -584,7 +584,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-07-16 14:23:57 -0700
+Last updated 2025-10-02 14:07:14 -0700
 </div>
 </div>
 </body>

git-patch-id.adoc

@@ -7,8 +7,8 @@ git-patch-id - Compute unique ID for a patch
 
 SYNOPSIS
 --------
-[verse]
-'git patch-id' [--stable | --unstable | --verbatim]
+[synopsis]
+git patch-id [--stable | --unstable | --verbatim]
 
 DESCRIPTION
 -----------
@@ -21,7 +21,7 @@ the same time also reasonably unique, i.e., two patches that have the same
 
 The main usecase for this command is to look for likely duplicate commits.
 
-When dealing with 'git diff-tree' output, it takes advantage of
+When dealing with `git diff-tree` output, it takes advantage of
 the fact that the patch is prefixed with the object name of the
 commit, and outputs two 40-byte hexadecimal strings.  The first
 string is the patch ID, and the second string is the commit ID.
@@ -30,35 +30,35 @@ This can be used to make a mapping from patch ID to commit ID.
 OPTIONS
 -------
 
---verbatim::
+`--verbatim`::
 	Calculate the patch-id of the input as it is given, do not strip
 	any whitespace.
 +
-This is the default if patchid.verbatim is true.
+This is the default if `patchid.verbatim` is `true`.
 
---stable::
+`--stable`::
 	Use a "stable" sum of hashes as the patch ID. With this option:
 +
 --
 - Reordering file diffs that make up a patch does not affect the ID.
   In particular, two patches produced by comparing the same two trees
-  with two different settings for "-O<orderfile>" result in the same
+  with two different settings for `-O<orderfile>` result in the same
   patch ID signature, thereby allowing the computed result to be used
   as a key to index some meta-information about the change between
   the two trees;
 
 - Result is different from the value produced by git 1.9 and older
-  or produced when an "unstable" hash (see --unstable below) is
+  or produced when an "unstable" hash (see `--unstable` below) is
   configured - even when used on a diff output taken without any use
-  of "-O<orderfile>", thereby making existing databases storing such
+  of `-O<orderfile>`, thereby making existing databases storing such
   "unstable" or historical patch-ids unusable.
 
 - All whitespace within the patch is ignored and does not affect the id.
 --
 +
-This is the default if patchid.stable is set to true.
+This is the default if `patchid.stable` is set to `true`.
 
---unstable::
+`--unstable`::
 	Use an "unstable" hash as the patch ID. With this option,
 	the result produced is compatible with the patch-id value produced
 	by git 1.9 and older and whitespace is ignored.  Users with pre-existing

git-patch-id.html

@@ -452,7 +452,7 @@ <h2 id="_name">NAME</h2>
 <h2 id="_synopsis">SYNOPSIS</h2>
 <div class="sectionbody">
 <div class="verseblock">
-<pre class="content"><em>git patch-id</em> [--stable | --unstable | --verbatim]</pre>
+<pre class="content"><code>git</code> <code>patch-id</code> [<code>--stable</code> | <code>--unstable</code> | <code>--verbatim</code>]</pre>
 </div>
 </div>
 </div>
@@ -472,7 +472,7 @@ <h2 id="_description">DESCRIPTION</h2>
 <p>The main usecase for this command is to look for likely duplicate commits.</p>
 </div>
 <div class="paragraph">
-<p>When dealing with <em>git diff-tree</em> output, it takes advantage of
+<p>When dealing with <code>git</code> <code>diff-tree</code> output, it takes advantage of
 the fact that the patch is prefixed with the object name of the
 commit, and outputs two 40-byte hexadecimal strings.  The first
 string is the patch ID, and the second string is the commit ID.
@@ -485,15 +485,15 @@ <h2 id="_options">OPTIONS</h2>
 <div class="sectionbody">
 <div class="dlist">
 <dl>
-<dt class="hdlist1">--verbatim</dt>
+<dt class="hdlist1"><code>--verbatim</code></dt>
 <dd>
 <p>Calculate the patch-id of the input as it is given, do not strip
 any whitespace.</p>
 <div class="paragraph">
-<p>This is the default if patchid.verbatim is true.</p>
+<p>This is the default if <code>patchid.verbatim</code> is <code>true</code>.</p>
 </div>
 </dd>
-<dt class="hdlist1">--stable</dt>
+<dt class="hdlist1"><code>--stable</code></dt>
 <dd>
 <p>Use a "stable" sum of hashes as the patch ID. With this option:</p>
 <div class="openblock">
@@ -503,16 +503,16 @@ <h2 id="_options">OPTIONS</h2>
 <li>
 <p>Reordering file diffs that make up a patch does not affect the ID.
 In particular, two patches produced by comparing the same two trees
-with two different settings for "-O&lt;orderfile&gt;" result in the same
+with two different settings for <code>-O</code><em>&lt;orderfile&gt;</em> result in the same
 patch ID signature, thereby allowing the computed result to be used
 as a key to index some meta-information about the change between
 the two trees;</p>
 </li>
 <li>
 <p>Result is different from the value produced by git 1.9 and older
-or produced when an "unstable" hash (see --unstable below) is
+or produced when an "unstable" hash (see <code>--unstable</code> below) is
 configured - even when used on a diff output taken without any use
-of "-O&lt;orderfile&gt;", thereby making existing databases storing such
+of <code>-O</code><em>&lt;orderfile&gt;</em>, thereby making existing databases storing such
 "unstable" or historical patch-ids unusable.</p>
 </li>
 <li>
@@ -523,10 +523,10 @@ <h2 id="_options">OPTIONS</h2>
 </div>
 </div>
 <div class="paragraph">
-<p>This is the default if patchid.stable is set to true.</p>
+<p>This is the default if <code>patchid.stable</code> is set to <code>true</code>.</p>
 </div>
 </dd>
-<dt class="hdlist1">--unstable</dt>
+<dt class="hdlist1"><code>--unstable</code></dt>
 <dd>
 <p>Use an "unstable" hash as the patch ID. With this option,
 the result produced is compatible with the patch-id value produced
@@ -552,7 +552,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-10-14 14:37:27 -0700
+Last updated 2025-11-03 07:28:51 -0800
 </div>
 </div>
 </body>

git-svn.html

@@ -1978,7 +1978,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-06-20 18:10:42 -0700
+Last updated 2025-08-25 14:46:08 -0700
 </div>
 </div>
 </body>

gitprotocol-http.html

@@ -1204,7 +1204,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-06-20 18:10:42 -0700
+Last updated 2025-08-25 14:46:08 -0700
 </div>
 </div>
 </body>