Autogenerated HTML docs for v2.49.0-281-g77d6e
diff --git a/RelNotes/2.50.0.adoc b/RelNotes/2.50.0.adoc
index b787dce..1023e61 100644
--- a/RelNotes/2.50.0.adoc
+++ b/RelNotes/2.50.0.adoc
@@ -15,6 +15,19 @@
* Incrementally updating multi-pack index files.
+ * "git reflog" learns "drop" subcommand, that discards the entire
+ reflog data for a ref.
+
+ * A new userdiff driver for ".ini" format configuration files has
+ been added.
+
+ * The job to coalesce loose objects into packfiles in "git
+ maintenance" now has configurable batch size.
+
+ * "git clone" still gave the message about the default branch name;
+ this message has been turned into an advice message that can be
+ turned off.
+
Performance, Internal Implementation, Development Support etc.
--------------------------------------------------------------
@@ -55,6 +68,9 @@
* CI update.
+ * The object layer has been updated to take an explicit repository
+ instance as a parameter in more code paths.
+
Fixes since v2.49
-----------------
@@ -107,6 +123,17 @@
which has been corrected.
(merge 93bab2d04b fr/vimdiff-layout-fixes later to maint).
+ * Fix our use of zlib corner cases.
+ (merge 1cb2f293f5 jk/zlib-inflate-fixes later to maint).
+
+ * Fix lockfile contention in reftable code on Windows.
+ (merge 0a3dceabf1 ps/mingw-creat-excl-fix later to maint).
+
+ * "git-merge-file" documentation source, which has lines that look
+ like conflict markers, lacked custom conflict marker size defined,
+ which has been corrected..
+ (merge d3b5832381 pw/custom-conflict-marker-size-for-merge-related-docs 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).
@@ -124,3 +151,5 @@
(merge 133d065dd6 ta/bulk-checkin-signed-compare-false-warning-fix later to maint).
(merge d2827dc31e es/meson-build-skip-coccinelle later to maint).
(merge ee8edb7156 dk/vimdiff-doc-fix later to maint).
+ (merge 107d889303 md/t1403-path-is-file later to maint).
+ (merge abd4192b07 js/comma-semicolon-confusion later to maint).
diff --git a/git-config.html b/git-config.html
index 1de473d..39dc4e2 100644
--- a/git-config.html
+++ b/git-config.html
@@ -6646,6 +6646,12 @@
loose objects is at least the value of <code>maintenance.loose-objects.auto</code>.
The default value is 100.</p>
</dd>
+<dt class="hdlist1">maintenance.loose-objects.batchSize</dt>
+<dd>
+<p>This integer config option controls the maximum number of loose objects
+written into a packfile during the <code>loose-objects</code> task. The default is
+fifty thousand. Use value <code>0</code> to indicate no limit.</p>
+</dd>
<dt class="hdlist1">maintenance.incremental-repack.auto</dt>
<dd>
<p>This integer config option controls how often the <code>incremental-repack</code>
diff --git a/git-maintenance.adoc b/git-maintenance.adoc
index 0450d74..c90b370 100644
--- a/git-maintenance.adoc
+++ b/git-maintenance.adoc
@@ -126,13 +126,17 @@
objects that already exist in a pack-file; concurrent Git processes
will examine the pack-file for the object data instead of the loose
object. Second, it creates a new pack-file (starting with "loose-")
- containing a batch of loose objects. The batch size is limited to 50
- thousand objects to prevent the job from taking too long on a
- repository with many loose objects. The `gc` task writes unreachable
- objects as loose objects to be cleaned up by a later step only if
- they are not re-added to a pack-file; for this reason it is not
- advisable to enable both the `loose-objects` and `gc` tasks at the
- same time.
+ containing a batch of loose objects.
++
+The batch size defaults to fifty thousand objects to prevent the job from
+taking too long on a repository with many loose objects. Use the
+`maintenance.loose-objects.batchSize` config option to adjust this size,
+including a value of `0` to remove the limit.
++
+The `gc` task writes unreachable objects as loose objects to be cleaned up
+by a later step only if they are not re-added to a pack-file; for this
+reason it is not advisable to enable both the `loose-objects` and `gc`
+tasks at the same time.
incremental-repack::
The `incremental-repack` job repacks the object directory
diff --git a/git-maintenance.html b/git-maintenance.html
index 8e0f7e0..d0b8d38 100644
--- a/git-maintenance.html
+++ b/git-maintenance.html
@@ -613,13 +613,19 @@
objects that already exist in a pack-file; concurrent Git processes
will examine the pack-file for the object data instead of the loose
object. Second, it creates a new pack-file (starting with "loose-")
-containing a batch of loose objects. The batch size is limited to 50
-thousand objects to prevent the job from taking too long on a
-repository with many loose objects. The <code>gc</code> task writes unreachable
-objects as loose objects to be cleaned up by a later step only if
-they are not re-added to a pack-file; for this reason it is not
-advisable to enable both the <code>loose-objects</code> and <code>gc</code> tasks at the
-same time.</p>
+containing a batch of loose objects.</p>
+<div class="paragraph">
+<p>The batch size defaults to fifty thousand objects to prevent the job from
+taking too long on a repository with many loose objects. Use the
+<code>maintenance.loose-objects.batchSize</code> config option to adjust this size,
+including a value of <code>0</code> to remove the limit.</p>
+</div>
+<div class="paragraph">
+<p>The <code>gc</code> task writes unreachable objects as loose objects to be cleaned up
+by a later step only if they are not re-added to a pack-file; for this
+reason it is not advisable to enable both the <code>loose-objects</code> and <code>gc</code>
+tasks at the same time.</p>
+</div>
</dd>
<dt class="hdlist1">incremental-repack</dt>
<dd>
@@ -1038,6 +1044,12 @@
loose objects is at least the value of <code>maintenance.loose-objects.auto</code>.
The default value is 100.</p>
</dd>
+<dt class="hdlist1">maintenance.loose-objects.batchSize</dt>
+<dd>
+<p>This integer config option controls the maximum number of loose objects
+written into a packfile during the <code>loose-objects</code> task. The default is
+fifty thousand. Use value <code>0</code> to indicate no limit.</p>
+</dd>
<dt class="hdlist1">maintenance.incremental-repack.auto</dt>
<dd>
<p>This integer config option controls how often the <code>incremental-repack</code>
@@ -1063,7 +1075,7 @@
</div>
<div id="footer">
<div id="footer-text">
-Last updated 2025-02-14 21:38:14 -0800
+Last updated 2025-04-15 14:25:08 -0700
</div>
</div>
</body>
diff --git a/git-reflog.adoc b/git-reflog.adoc
index a929c52..b55c060 100644
--- a/git-reflog.adoc
+++ b/git-reflog.adoc
@@ -16,6 +16,7 @@
[--dry-run | -n] [--verbose] [--all [--single-worktree] | <refs>...]
'git reflog delete' [--rewrite] [--updateref]
[--dry-run | -n] [--verbose] <ref>@{<specifier>}...
+'git reflog drop' [--all [--single-worktree] | <refs>...]
'git reflog exists' <ref>
DESCRIPTION
@@ -48,10 +49,14 @@
This is typically not used directly by end users -- instead, see
linkgit:git-gc[1].
-The "delete" subcommand deletes single entries from the reflog. Its
-argument must be an _exact_ entry (e.g. "`git reflog delete
-master@{2}`"). This subcommand is also typically not used directly by
-end users.
+The "delete" subcommand deletes single entries from the reflog, but
+not the reflog itself. Its argument must be an _exact_ entry (e.g. "`git
+reflog delete master@{2}`"). This subcommand is also typically not used
+directly by end users.
+
+The "drop" subcommand completely removes the reflog for the specified
+references. This is in contrast to "expire" and "delete", both of which
+can be used to delete reflog entries, but not the reflog itself.
The "exists" subcommand checks whether a ref has a reflog. It exits
with zero status if the reflog exists, and non-zero status if it does
@@ -132,6 +137,16 @@
`--dry-run`, and `--verbose`, with the same meanings as when they are
used with `expire`.
+Options for `drop`
+~~~~~~~~~~~~~~~~~~~~
+
+--all::
+ Drop the reflogs of all references from all worktrees.
+
+--single-worktree::
+ By default when `--all` is specified, reflogs from all working
+ trees are dropped. This option limits the processing to reflogs
+ from the current working tree only.
GIT
---
diff --git a/git-reflog.html b/git-reflog.html
index a4803a5..4454067 100644
--- a/git-reflog.html
+++ b/git-reflog.html
@@ -459,6 +459,7 @@
[--dry-run | -n] [--verbose] [--all [--single-worktree] | <refs>…​]
<em>git reflog delete</em> [--rewrite] [--updateref]
[--dry-run | -n] [--verbose] <ref>@{<specifier>}…​
+<em>git reflog drop</em> [--all [--single-worktree] | <refs>…​]
<em>git reflog exists</em> <ref></pre>
</div>
</div>
@@ -501,10 +502,15 @@
<a href="git-gc.html">git-gc(1)</a>.</p>
</div>
<div class="paragraph">
-<p>The "delete" subcommand deletes single entries from the reflog. Its
-argument must be an <em>exact</em> entry (e.g. "<code>git</code> <code>reflog</code> <code>delete</code>
-<code>master@</code>{2}"). This subcommand is also typically not used directly by
-end users.</p>
+<p>The "delete" subcommand deletes single entries from the reflog, but
+not the reflog itself. Its argument must be an <em>exact</em> entry (e.g. "<code>git</code>
+<code>reflog</code> <code>delete</code> <code>master@</code>{2}"). This subcommand is also typically not used
+directly by end users.</p>
+</div>
+<div class="paragraph">
+<p>The "drop" subcommand completely removes the reflog for the specified
+references. This is in contrast to "expire" and "delete", both of which
+can be used to delete reflog entries, but not the reflog itself.</p>
</div>
<div class="paragraph">
<p>The "exists" subcommand checks whether a ref has a reflog. It exits
@@ -601,6 +607,24 @@
<code>--dry-run</code>, and <code>--verbose</code>, with the same meanings as when they are
used with <code>expire</code>.</p>
</div>
+<div class="paragraph">
+<p>Options for <code>drop</code>
+<sub>~</sub><sub>~</sub><sub>~</sub><sub>~</sub><sub>~</sub><sub>~</sub>~~</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">--all</dt>
+<dd>
+<p>Drop the reflogs of all references from all worktrees.</p>
+</dd>
+<dt class="hdlist1">--single-worktree</dt>
+<dd>
+<p>By default when <code>--all</code> is specified, reflogs from all working
+trees are dropped. This option limits the processing to reflogs
+from the current working tree only.</p>
+</dd>
+</dl>
+</div>
</div>
</div>
</div>
@@ -615,7 +639,7 @@
</div>
<div id="footer">
<div id="footer-text">
-Last updated 2025-02-14 21:38:14 -0800
+Last updated 2025-04-15 14:25:08 -0700
</div>
</div>
</body>
