Autogenerated HTML docs for v2.46.0-235-gb9849e

DecisionMaking.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Decision-Making Process in the Git Project</h1>
 <div class="details">
-<span id="revdate">2024-08-15</span>
+<span id="revdate">2024-08-16</span>
 </div>
 </div>
 <div id="content">

MyFirstContribution.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>My First Contribution to the Git Project</h1>
 <div class="details">
-<span id="revdate">2024-08-15</span>
+<span id="revdate">2024-08-16</span>
 </div>
 </div>
 <div id="content">

MyFirstObjectWalk.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>My First Object Walk</h1>
 <div class="details">
-<span id="revdate">2024-08-15</span>
+<span id="revdate">2024-08-16</span>
 </div>
 </div>
 <div id="content">

RelNotes/2.46.1.txt

@@ -0,0 +1,37 @@
+Git 2.46.1 Release Notes
+========================
+
+This release is primarily to merge fixes accumulated on the 'master'
+front to prepare for 2.47 release that are still relevant to 2.46.x
+maintenance track.
+
+Fixes since Git 2.46
+--------------------
+
+ * "git checkout --ours" (no other arguments) complained that the
+   option is incompatible with branch switching, which is technically
+   correct, but found confusing by some users.  It now says that the
+   user needs to give pathspec to specify what paths to checkout.
+
+ * It has been documented that we avoid "VAR=VAL shell_func" and why.
+
+ * "git add -p" by users with diff.suppressBlankEmpty set to true
+   failed to parse the patch that represents an unmodified empty line
+   with an empty line (not a line with a single space on it), which
+   has been corrected.
+
+ * "git rebase --help" referred to "offset" (the difference between
+   the location a change was taken from and the change gets replaced)
+   incorrectly and called it "fuzz", which has been corrected.
+
+ * "git notes add -m '' --allow-empty" and friends that take prepared
+   data to create notes should not invoke an editor, but it started
+   doing so since Git 2.42, which has been corrected.
+
+ * An expensive operation to prepare tracing was done in re-encoding
+   code path even when the tracing was not requested, which has been
+   corrected.
+
+ * Perforce tests have been updated.
+
+Also contains minor documentation updates and code clean-ups.

RelNotes/2.47.0.txt

@@ -75,31 +75,25 @@ Fixes since v2.46
    failed to parse the patch that represents an unmodified empty line
    with an empty line (not a line with a single space on it), which
    has been corrected.
-   (merge 60cf761ed1 pw/add-patch-with-suppress-blank-empty later to maint).
 
  * "git checkout --ours" (no other arguments) complained that the
    option is incompatible with branch switching, which is technically
    correct, but found confusing by some users.  It now says that the
    user needs to give pathspec to specify what paths to checkout.
-   (merge d1e6c61272 jc/checkout-no-op-switch-errors later to maint).
 
  * It has been documented that we avoid "VAR=VAL shell_func" and why.
-   (merge 728a1962cd jc/doc-one-shot-export-with-shell-func later to maint).
 
  * "git rebase --help" referred to "offset" (the difference between
    the location a change was taken from and the change gets replaced)
    incorrectly and called it "fuzz", which has been corrected.
-   (merge 70058db385 jc/doc-rebase-fuzz-vs-offset-fix later to maint).
 
  * "git notes add -m '' --allow-empty" and friends that take prepared
    data to create notes should not invoke an editor, but it started
    doing so since Git 2.42, which has been corrected.
-   (merge 8b426c84f3 dd/notes-empty-no-edit-by-default later to maint).
 
  * An expensive operation to prepare tracing was done in re-encoding
    code path even when the tracing was not requested, which has been
    corrected.
-   (merge 63ad8dbf16 dh/encoding-trace-optim later to maint).
 
  * More leakfixes.
    (merge f30bfafcd4 ps/leakfixes-part-3 later to maint).
@@ -143,11 +137,7 @@ Fixes since v2.46
    (merge a77554ea09 xx/diff-tree-remerge-diff-fix later to maint).
 
  * Other code cleanup, docfix, build fix, etc.
-   (merge 8db8786fc2 jt/doc-post-receive-hook-update later to maint).
-   (merge 1c473dd6af tn/doc-commit-fix later to maint).
    (merge bb0498b1bb jc/how-to-maintain-updates later to maint).
-   (merge 6e71d6ac7c ks/unit-test-comment-typofix later to maint).
-   (merge 63ee933383 ps/p4-tests-updates later to maint).
    (merge 7c7516b8db jc/jl-git-no-advice-fix later to maint).
    (merge c3d034df16 jc/leakfix-hashfile later to maint).
    (merge d98d9c77e5 jc/leakfix-mailmap later to maint).

ReviewingGuidelines.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Reviewing Patches in the Git Project</h1>
 <div class="details">
-<span id="revdate">2024-08-15</span>
+<span id="revdate">2024-08-16</span>
 </div>
 </div>
 <div id="content">

SubmittingPatches.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Submitting Patches</h1>
 <div class="details">
-<span id="revdate">2024-08-15</span>
+<span id="revdate">2024-08-16</span>
 </div>
 </div>
 <div id="content">

ToolsForGit.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Tools for developing Git</h1>
 <div class="details">
-<span id="revdate">2024-08-15</span>
+<span id="revdate">2024-08-16</span>
 </div>
 </div>
 <div id="content">

everyday.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Everyday Git With 20 Commands Or So</h1>
 <div class="details">
-<span id="revdate">2024-08-15</span>
+<span id="revdate">2024-08-16</span>
 </div>
 </div>
 <div id="content">

fsck-msgids.txt

@@ -19,6 +19,12 @@
 `badParentSha1`::
 	(ERROR) A commit object has a bad parent sha1.
 
+`badRefFiletype`::
+	(ERROR) A ref has a bad file type.
+
+`badRefName`::
+	(ERROR) A ref has an invalid format.
+
 `badTagName`::
 	(INFO) A tag has an invalid format.
 

git-fsck.html

@@ -768,6 +768,14 @@ <h2 id="_fsck_messages">FSCK MESSAGES</h2>
 <dd>
 <p>(ERROR) A commit object has a bad parent sha1.</p>
 </dd>
+<dt class="hdlist1"><code>badRefFiletype</code></dt>
+<dd>
+<p>(ERROR) A ref has a bad file type.</p>
+</dd>
+<dt class="hdlist1"><code>badRefName</code></dt>
+<dd>
+<p>(ERROR) A ref has an invalid format.</p>
+</dd>
 <dt class="hdlist1"><code>badTagName</code></dt>
 <dd>
 <p>(INFO) A tag has an invalid format.</p>

git-refs.html

@@ -451,7 +451,8 @@ <h2 id="_name">NAME</h2>
 <h2 id="_synopsis">SYNOPSIS</h2>
 <div class="sectionbody">
 <div class="verseblock">
-<pre class="content"><em>git refs migrate</em> --ref-format=&lt;format&gt; [--dry-run]</pre>
+<pre class="content"><em>git refs migrate</em> --ref-format=&lt;format&gt; [--dry-run]
+<em>git refs verify</em> [--strict] [--verbose]</pre>
 </div>
 </div>
 </div>
@@ -472,6 +473,10 @@ <h2 id="_commands">COMMANDS</h2>
 <dd>
 <p>Migrate ref store between different formats.</p>
 </dd>
+<dt class="hdlist1">verify</dt>
+<dd>
+<p>Verify reference database consistency.</p>
+</dd>
 </dl>
 </div>
 </div>
@@ -509,6 +514,22 @@ <h2 id="_options">OPTIONS</h2>
 </dd>
 </dl>
 </div>
+<div class="paragraph">
+<p>The following options are specific to <em>git refs verify</em>:</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">--strict</dt>
+<dd>
+<p>Enable stricter error checking. This will cause warnings to be
+reported as errors. See <a href="git-fsck.html">git-fsck(1)</a>.</p>
+</dd>
+<dt class="hdlist1">--verbose</dt>
+<dd>
+<p>When verifying the reference database consistency, be chatty.</p>
+</dd>
+</dl>
+</div>
 </div>
 </div>
 <div class="sect1">
@@ -550,7 +571,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-06-17 16:42:55 -0700
+Last updated 2024-08-16 14:07:46 -0700
 </div>
 </div>
 </body>

git-refs.txt

@@ -10,6 +10,7 @@ SYNOPSIS
 --------
 [verse]
 'git refs migrate' --ref-format=<format> [--dry-run]
+'git refs verify' [--strict] [--verbose]
 
 DESCRIPTION
 -----------
@@ -22,6 +23,9 @@ COMMANDS
 migrate::
 	Migrate ref store between different formats.
 
+verify::
+	Verify reference database consistency.
+
 OPTIONS
 -------
 
@@ -39,6 +43,15 @@ include::ref-storage-format.txt[]
 	can be used to double check that the migration works as expected before
 	performing the actual migration.
 
+The following options are specific to 'git refs verify':
+
+--strict::
+	Enable stricter error checking. This will cause warnings to be
+	reported as errors. See linkgit:git-fsck[1].
+
+--verbose::
+	When verifying the reference database consistency, be chatty.
+
 KNOWN LIMITATIONS
 -----------------
 

git-remote-helpers.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>git-remote-helpers</h1>
 <div class="details">
-<span id="revdate">2024-08-15</span>
+<span id="revdate">2024-08-16</span>
 </div>
 </div>
 <div id="content">

howto/keep-canonical-history-correct.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Keep authoritative canonical history correct with git pull</h1>
 <div class="details">
-<span id="revdate">2024-08-15</span>
+<span id="revdate">2024-08-16</span>
 </div>
 </div>
 <div id="content">
@@ -705,7 +705,7 @@ <h1>Keep authoritative canonical history correct with git pull</h1>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-08-16 10:29:08 -0700
+Last updated 2024-08-16 14:08:06 -0700
 </div>
 </div>
 </body>

howto/maintain-git.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>How to maintain Git</h1>
 <div class="details">
-<span id="revdate">2024-08-15</span>
+<span id="revdate">2024-08-16</span>
 </div>
 </div>
 <div id="content">
@@ -1235,7 +1235,7 @@ <h3 id="_preparing_a_merge_fix">Preparing a "merge-fix"</h3>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-08-16 10:29:08 -0700
+Last updated 2024-08-16 14:08:06 -0700
 </div>
 </div>
 </body>

howto/new-command.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>How to integrate new subcommands</h1>
 <div class="details">
-<span id="revdate">2024-08-15</span>
+<span id="revdate">2024-08-16</span>
 </div>
 </div>
 <div id="content">
@@ -584,7 +584,7 @@ <h2 id="_integrating_a_command">Integrating a command</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-08-16 10:29:07 -0700
+Last updated 2024-08-16 14:08:05 -0700
 </div>
 </div>
 </body>

howto/rebase-from-internal-branch.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>How to rebase from an internal branch</h1>
 <div class="details">
-<span id="revdate">2024-08-15</span>
+<span id="revdate">2024-08-16</span>
 </div>
 </div>
 <div id="content">
@@ -656,7 +656,7 @@ <h1>How to rebase from an internal branch</h1>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-08-16 10:29:08 -0700
+Last updated 2024-08-16 14:08:06 -0700
 </div>
 </div>
 </body>

howto/rebuild-from-update-hook.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>How to rebuild from update hook</h1>
 <div class="details">
-<span id="revdate">2024-08-15</span>
+<span id="revdate">2024-08-16</span>
 </div>
 </div>
 <div id="content">
@@ -563,7 +563,7 @@ <h1>How to rebuild from update hook</h1>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-08-16 10:29:08 -0700
+Last updated 2024-08-16 14:08:06 -0700
 </div>
 </div>
 </body>

howto/recover-corrupted-blob-object.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>How to recover a corrupted blob object</h1>
 <div class="details">
-<span id="revdate">2024-08-15</span>
+<span id="revdate">2024-08-16</span>
 </div>
 </div>
 <div id="content">
@@ -641,7 +641,7 @@ <h1>How to recover a corrupted blob object</h1>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-08-16 10:29:07 -0700
+Last updated 2024-08-16 14:08:06 -0700
 </div>
 </div>
 </body>

howto/recover-corrupted-object-harder.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>How to recover an object from scratch</h1>
 <div class="details">
-<span id="revdate">2024-08-15</span>
+<span id="revdate">2024-08-16</span>
 </div>
 </div>
 <div id="content">
@@ -967,7 +967,7 @@ <h2 id="_the_adventure_continues">The adventure continues&#8230;&#8203;</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-08-16 10:29:07 -0700
+Last updated 2024-08-16 14:08:06 -0700
 </div>
 </div>
 </body>