Autogenerated HTML docs for v2.38.0-68-ge8570

25 files changed, 152 insertions, 65 deletions

diff --git a/RelNotes/2.39.0.txt b/RelNotes/2.39.0.txt
index 3d27b72ef..a26c82444 100644
--- a/RelNotes/2.39.0.txt
+++ b/RelNotes/2.39.0.txt
@@ -1,7 +1,15 @@
 Git v2.39 Release Notes
 =======================
 
+UI, Workflows & Features
+------------------------
+
+ * "git grep" learned to expand the sparse-index more lazily and on
+   demand in a sparse checkout.
+
+
 Performance, Internal Implementation, Development Support etc.
+--------------------------------------------------------------
 
  * With a bit of header twiddling, use the native regexp library on
    macOS instead of the compat/ one.
@@ -11,6 +19,13 @@ Performance, Internal Implementation, Development Support etc.
  * Sources related to fuzz testing have been moved down to their own
    directory.
 
+ * Most credential helpers ignored unknown entries in a credential
+   description, but a few died upon seeing them.  The latter were
+   taught to ignore them, too
+
+ * "scalar unregister" in a repository that is already been
+   unregistered reported an error.
+
 
 Fixes since v2.38
 -----------------
@@ -19,4 +34,41 @@ Fixes since v2.38
    accesses, which has been corrected.
    (merge 4a6ed30f96 vd/fix-unaligned-read-index-v4 later to maint).
 
+ * Fix messages incorrectly marked for translation.
+   (merge 02cb8b9ee3 ah/fsmonitor-daemon-usage-non-l10n later to maint).
+
+ * "git fsck" failed to release contents of tree objects already used
+   from the memory, which has been fixed.
+   (merge 51b27747e5 jk/fsck-on-diet later to maint).
+
+ * "git clone" did not like to see the "--bare" and the "--origin"
+   options used together without a good reason.
+   (merge 3b910d6e29 jk/clone-allow-bare-and-o-together later to maint).
+
+ * "git remote rename" failed to rename a remote without fetch
+   refspec, which has been corrected.
+   (merge 5a97b38109 jk/remote-rename-without-fetch-refspec later to maint).
+
+ * Documentation on various Boolean GIT_* environment variables have
+   been clarified.
+   (merge 819fb68222 jc/environ-docs later to maint).
+
+ * "git rebase -i" can mistakenly attempt to apply a fixup to a commit
+   itself, which has been corrected.
+   (merge 3e367a5f2f ja/rebase-i-avoid-amending-self later to maint).
+
+ * "git multi-pack-index repack/expire" used to repack unreachable
+   cruft into a new pack, which have been corrected.
+   (merge b62ad5681f tb/midx-repack-ignore-cruft-packs later to maint).
+
+ * In read-only repositories, "git merge-tree" tried to come up with a
+   merge result tree object, which it failed (which is not wrong) and
+   led to a segfault (which is bad), which has been corrected.
+   (merge 92481d1b26 js/merge-ort-in-read-only-repo later to maint).
+
  * Other code cleanup, docfix, build fix, etc.
+   (merge c34a6bd291 so/diff-merges-cleanup later to maint).
+   (merge 5e7c8b75e7 ab/test-malloc-with-sanitize-leak later to maint).
+   (merge 2a905f8fa8 ah/branch-autosetupmerge-grammofix later to maint).
+   (merge abcac2e19f rj/ref-filter-get-head-description-leakfix later to maint).
+   (merge 71e5473493 hn/parse-worktree-ref later to maint).
diff --git a/git-config.html b/git-config.html
index 02c22fd21..c9f5c855f 100644
--- a/git-config.html
+++ b/git-config.html
@@ -7659,9 +7659,9 @@ log.diffMerges
 </dt>

 <dd>

 <p>

-        Set default diff format to be used for merge commits. See

-        <code>--diff-merges</code> in <a href="git-log.html">git-log(1)</a> for details.

-        Defaults to <code>separate</code>.

+        Set diff format to be used when <code>--diff-merges=on</code> is

+        specified, see <code>--diff-merges</code> in <a href="git-log.html">git-log(1)</a> for

+        details. Defaults to <code>separate</code>.

 </p>

 </dd>

 <dt class="hdlist1">

diff --git a/git-log.html b/git-log.html
index a1f3e1e16..843838c94 100644
--- a/git-log.html
+++ b/git-log.html
@@ -5405,9 +5405,9 @@ log.diffMerges
 </dt>

 <dd>

 <p>

-        Set default diff format to be used for merge commits. See

-        <code>--diff-merges</code> in <a href="git-log.html">git-log(1)</a> for details.

-        Defaults to <code>separate</code>.

+        Set diff format to be used when <code>--diff-merges=on</code> is

+        specified, see <code>--diff-merges</code> in <a href="git-log.html">git-log(1)</a> for

+        details. Defaults to <code>separate</code>.

 </p>

 </dd>

 <dt class="hdlist1">

diff --git a/git-maintenance.html b/git-maintenance.html
index eb388f895..9125e7aa8 100644
--- a/git-maintenance.html
+++ b/git-maintenance.html
@@ -751,7 +751,7 @@ git-maintenance(1) Manual Page
 <div class="verseblock">

 <pre class="content"><em>git maintenance</em> run [&lt;options&gt;]

 <em>git maintenance</em> start [--scheduler=&lt;scheduler&gt;]

-<em>git maintenance</em> (stop|register|unregister)</pre>

+<em>git maintenance</em> (stop|register|unregister) [&lt;options&gt;]</pre>

 <div class="attribution">

 </div></div>

 </div>

@@ -867,6 +867,9 @@ unregister
         only removes the repository from the configured list. It does not

         stop the background maintenance processes from running.

 </p>

+<div class="paragraph"><p>The <code>unregister</code> subcommand will report an error if the current repository

+is not already registered. Use the <code>--force</code> option to return success even

+when the current repository is not registered.</p></div>

 </dd>

 </dl></div>

 </div>

@@ -1356,7 +1359,7 @@ maintenance.incremental-repack.auto
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-09-14 13:23:11 PDT

+ 2022-10-10 14:40:17 PDT

 </div>

 </div>

 </body>

diff --git a/git-maintenance.txt b/git-maintenance.txt
index 9c630efe1..bb888690e 100644
--- a/git-maintenance.txt
+++ b/git-maintenance.txt
@@ -11,7 +11,7 @@ SYNOPSIS
 [verse]
 'git maintenance' run [<options>]
 'git maintenance' start [--scheduler=<scheduler>]
-'git maintenance' (stop|register|unregister)
+'git maintenance' (stop|register|unregister) [<options>]
 
 
 DESCRIPTION
@@ -79,6 +79,10 @@ unregister::
 	Remove the current repository from background maintenance. This
 	only removes the repository from the configured list. It does not
 	stop the background maintenance processes from running.
++
+The `unregister` subcommand will report an error if the current repository
+is not already registered. Use the `--force` option to return success even
+when the current repository is not registered.
 
 TASKS
 -----
diff --git a/git-multi-pack-index.html b/git-multi-pack-index.html
index 04fcbab0e..db7631bb8 100644
--- a/git-multi-pack-index.html
+++ b/git-multi-pack-index.html
@@ -861,9 +861,10 @@ expire
 </dt>

 <dd>

 <p>

-        Delete the pack-files that are tracked  by the MIDX file, but

-        have no objects referenced by the MIDX. Rewrite the MIDX file

-        afterward to remove all references to these pack-files.

+        Delete the pack-files that are tracked by the MIDX file, but

+        have no objects referenced by the MIDX (with the exception of

+        <code>.keep</code> packs and cruft packs). Rewrite the MIDX file afterward

+        to remove all references to these pack-files.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -957,7 +958,7 @@ multi-pack-index feature and its file format.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-08-18 14:11:07 PDT

+ 2022-10-10 14:40:17 PDT

 </div>

 </div>

 </body>

diff --git a/git-multi-pack-index.txt b/git-multi-pack-index.txt
index a48c3d5ea..3696506eb 100644
--- a/git-multi-pack-index.txt
+++ b/git-multi-pack-index.txt
@@ -70,9 +70,10 @@ verify::
 	Verify the contents of the MIDX file.
 
 expire::
-	Delete the pack-files that are tracked 	by the MIDX file, but
-	have no objects referenced by the MIDX. Rewrite the MIDX file
-	afterward to remove all references to these pack-files.
+	Delete the pack-files that are tracked by the MIDX file, but
+	have no objects referenced by the MIDX (with the exception of
+	`.keep` packs and cruft packs). Rewrite the MIDX file afterward
+	to remove all references to these pack-files.
 
 repack::
 	Create a new pack-file containing objects in small pack-files
diff --git a/git.html b/git.html
index 066b525ab..ee7a000db 100644
--- a/git.html
+++ b/git.html
@@ -2848,7 +2848,11 @@ HEAD
 <div class="sect1">

 <h2 id="_environment_variables">Environment Variables</h2>

 <div class="sectionbody">

-<div class="paragraph"><p>Various Git commands use the following environment variables:</p></div>

+<div class="paragraph"><p>Various Git commands pay attention to environment variables and change

+their behavior.  The environment variables marked as "Boolean" take

+their values the same way as Boolean valued configuration variables, e.g.

+"true", "yes", "on" and positive numbers are taken as "yes".</p></div>

+<div class="paragraph"><p>Here are the variables:</p></div>

 <div class="sect2">

 <h3 id="_the_git_repository">The Git Repository</h3>

 <div class="paragraph"><p>These environment variables apply to <em>all</em> core Git commands. Nb: it

@@ -2860,7 +2864,7 @@ Git so take care if using a foreign front-end.</p></div>
 </dt>

 <dd>

 <p>

-        This environment allows the specification of an alternate

+        This environment variable specifies an alternate

         index file. If not specified, the default of <code>$GIT_DIR/index</code>

         is used.

 </p>

@@ -2870,8 +2874,8 @@ Git so take care if using a foreign front-end.</p></div>
 </dt>

 <dd>

 <p>

-        This environment variable allows the specification of an index

-        version for new repositories.  It won&#8217;t affect existing index

+        This environment variable specifies what index version is used

+        when writing the index file out.  It won&#8217;t affect existing index

         files.  By default index file version 2 or 3 is used. See

         <a href="git-update-index.html">git-update-index(1)</a> for more information.

 </p>

@@ -2962,7 +2966,7 @@ double-quotes and respecting backslash escapes. E.g., the value
         When run in a directory that does not have ".git" repository

         directory, Git tries to find such a directory in the parent

         directories to find the top of the working tree, but by default it

-        does not cross filesystem boundaries.  This environment variable

+        does not cross filesystem boundaries.  This Boolean environment variable

         can be set to true to tell Git not to stop at filesystem

         boundaries.  Like <code>GIT_CEILING_DIRECTORIES</code>, this will not affect

         an explicit repository directory set via <code>GIT_DIR</code> or on the

@@ -3243,6 +3247,16 @@ for further details.</p></div>
 </p>

 </dd>

 <dt class="hdlist1">

+<code>GIT_SSL_NO_VERIFY</code>

+</dt>

+<dd>

+<p>

+        Setting and exporting this environment variable to any value

+        tells Git not to verify the SSL certificate when fetching or

+        pushing over HTTPS.

+</p>

+</dd>

+<dt class="hdlist1">

 <code>GIT_ASKPASS</code>

 </dt>

 <dd>

@@ -3259,7 +3273,7 @@ for further details.</p></div>
 </dt>

 <dd>

 <p>

-        If this environment variable is set to <code>0</code>, git will not prompt

+        If this Boolean environment variable is set to false, git will not prompt

         on the terminal (e.g., when asking for HTTP authentication).

 </p>

 </dd>

@@ -3286,10 +3300,10 @@ for further details.</p></div>
 <dd>

 <p>

         Whether to skip reading settings from the system-wide

-        <code>$(prefix)/etc/gitconfig</code> file.  This environment variable can

+        <code>$(prefix)/etc/gitconfig</code> file.  This Boolean environment variable can

         be used along with <code>$HOME</code> and <code>$XDG_CONFIG_HOME</code> to create a

         predictable environment for a picky script, or you can set it

-        temporarily to avoid using a buggy <code>/etc/gitconfig</code> file while

+        to true to temporarily avoid using a buggy <code>/etc/gitconfig</code> file while

         waiting for someone with sufficient permissions to fix it.

 </p>

 </dd>

@@ -3298,6 +3312,7 @@ for further details.</p></div>
 </dt>

 <dd>

 <p>

+

         If this environment variable is set to "1", then commands such

         as <em>git blame</em> (in incremental mode), <em>git rev-list</em>, <em>git log</em>,

         <em>git check-attr</em> and <em>git check-ignore</em> will

@@ -3501,7 +3516,7 @@ for full details.</p></div>
 <p>

         By default, when tracing is activated, Git redacts the values of

         cookies, the "Authorization:" header, the "Proxy-Authorization:"

-        header and packfile URIs. Set this variable to <code>0</code> to prevent this

+        header and packfile URIs. Set this Boolean environment variable to false to prevent this

         redaction.

 </p>

 </dd>

@@ -3510,7 +3525,7 @@ for full details.</p></div>
 </dt>

 <dd>

 <p>

-        Setting this variable to <code>1</code> will cause Git to treat all

+        Setting this Boolean environment variable to true will cause Git to treat all

         pathspecs literally, rather than as glob patterns. For example,

         running <code>GIT_LITERAL_PATHSPECS=1 git log -- '*.c'</code> will search

         for commits that touch the path <code>*.c</code>, not any paths that the

@@ -3524,7 +3539,7 @@ for full details.</p></div>
 </dt>

 <dd>

 <p>

-        Setting this variable to <code>1</code> will cause Git to treat all

+        Setting this Boolean environment variable to true will cause Git to treat all

         pathspecs as glob patterns (aka "glob" magic).

 </p>

 </dd>

@@ -3533,7 +3548,7 @@ for full details.</p></div>
 </dt>

 <dd>

 <p>

-        Setting this variable to <code>1</code> will cause Git to treat all

+        Setting this Boolean environment variable to true will cause Git to treat all

         pathspecs as literal (aka "literal" magic).

 </p>

 </dd>

@@ -3542,7 +3557,7 @@ for full details.</p></div>
 </dt>

 <dd>

 <p>

-        Setting this variable to <code>1</code> will cause Git to treat all

+        Setting this Boolean environment variable to true will cause Git to treat all

         pathspecs as case-insensitive.

 </p>

 </dd>

@@ -3566,7 +3581,7 @@ for full details.</p></div>
 </dt>

 <dd>

 <p>

-        If set to <code>0</code>, ignore broken or badly named refs when iterating

+        If this Boolean environment variable is set to false, ignore broken or badly named refs when iterating

         over lists of refs. Normally Git will try to include any such

         refs, which may cause some operations to fail. This is usually

         preferable, as potentially destructive operations (e.g.,

@@ -3595,7 +3610,7 @@ for full details.</p></div>
 </dt>

 <dd>

 <p>

-        Set to 0 to prevent protocols used by fetch/push/clone which are

+        Set this Boolean environment variable to false to prevent protocols used by fetch/push/clone which are

         configured to the <code>user</code> state.  This is useful to restrict recursive

         submodule initialization from an untrusted repository or for programs

         which feed potentially-untrusted URLS to git commands.  See

@@ -3631,7 +3646,7 @@ be in the future).</p></div>
 </dt>

 <dd>

 <p>

-        If set to <code>0</code>, Git will complete any requested operation without

+        If this Boolean environment variable is set to false, Git will complete any requested operation without

         performing any optional sub-operations that require taking a lock.

         For example, this will prevent <code>git status</code> from refreshing the

         index as a side effect. This is useful for processes running in

@@ -3792,7 +3807,7 @@ the Git Security mailing list &lt;<a href="mailto:git-security@googlegroups.com"
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-09-21 15:44:34 PDT

+ 2022-10-10 14:40:17 PDT

 </div>

 </div>

 </body>

diff --git a/git.txt b/git.txt
index 0c15ef3a8..1d33e083a 100644
--- a/git.txt
+++ b/git.txt
@@ -458,7 +458,12 @@ Please see linkgit:gitglossary[7].
 
 Environment Variables
 ---------------------
-Various Git commands use the following environment variables:
+Various Git commands pay attention to environment variables and change
+their behavior.  The environment variables marked as "Boolean" take
+their values the same way as Boolean valued configuration variables, e.g.
+"true", "yes", "on" and positive numbers are taken as "yes".
+
+Here are the variables:
 
 The Git Repository
 ~~~~~~~~~~~~~~~~~~
@@ -467,13 +472,13 @@ is worth noting that they may be used/overridden by SCMS sitting above
 Git so take care if using a foreign front-end.
 
 `GIT_INDEX_FILE`::
-	This environment allows the specification of an alternate
+	This environment variable specifies an alternate
 	index file. If not specified, the default of `$GIT_DIR/index`
 	is used.
 
 `GIT_INDEX_VERSION`::
-	This environment variable allows the specification of an index
-	version for new repositories.  It won't affect existing index
+	This environment variable specifies what index version is used
+	when writing the index file out.  It won't affect existing index
 	files.  By default index file version 2 or 3 is used. See
 	linkgit:git-update-index[1] for more information.
 
@@ -530,7 +535,7 @@ double-quotes and respecting backslash escapes. E.g., the value
 	When run in a directory that does not have ".git" repository
 	directory, Git tries to find such a directory in the parent
 	directories to find the top of the working tree, but by default it
-	does not cross filesystem boundaries.  This environment variable
+	does not cross filesystem boundaries.  This Boolean environment variable
 	can be set to true to tell Git not to stop at filesystem
 	boundaries.  Like `GIT_CEILING_DIRECTORIES`, this will not affect
 	an explicit repository directory set via `GIT_DIR` or on the
@@ -682,6 +687,11 @@ for further details.
 	plink or tortoiseplink. This variable overrides the config setting
 	`ssh.variant` that serves the same purpose.
 
+`GIT_SSL_NO_VERIFY`::
+	Setting and exporting this environment variable to any value
+	tells Git not to verify the SSL certificate when fetching or
+	pushing over HTTPS.
+
 `GIT_ASKPASS`::
 	If this environment variable is set, then Git commands which need to
 	acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
@@ -690,7 +700,7 @@ for further details.
 	option in linkgit:git-config[1].
 
 `GIT_TERMINAL_PROMPT`::
-	If this environment variable is set to `0`, git will not prompt
+	If this Boolean environment variable is set to false, git will not prompt
 	on the terminal (e.g., when asking for HTTP authentication).
 
 `GIT_CONFIG_GLOBAL`::
@@ -705,13 +715,14 @@ for further details.
 
 `GIT_CONFIG_NOSYSTEM`::
 	Whether to skip reading settings from the system-wide
-	`$(prefix)/etc/gitconfig` file.  This environment variable can
+	`$(prefix)/etc/gitconfig` file.  This Boolean environment variable can
 	be used along with `$HOME` and `$XDG_CONFIG_HOME` to create a
 	predictable environment for a picky script, or you can set it
-	temporarily to avoid using a buggy `/etc/gitconfig` file while
+	to true to temporarily avoid using a buggy `/etc/gitconfig` file while
 	waiting for someone with sufficient permissions to fix it.
 
 `GIT_FLUSH`::
+// NEEDSWORK: make it into a usual Boolean environment variable
 	If this environment variable is set to "1", then commands such
 	as 'git blame' (in incremental mode), 'git rev-list', 'git log',
 	'git check-attr' and 'git check-ignore' will
@@ -852,11 +863,11 @@ for full details.
 `GIT_TRACE_REDACT`::
 	By default, when tracing is activated, Git redacts the values of
 	cookies, the "Authorization:" header, the "Proxy-Authorization:"
-	header and packfile URIs. Set this variable to `0` to prevent this
+	header and packfile URIs. Set this Boolean environment variable to false to prevent this
 	redaction.
 
 `GIT_LITERAL_PATHSPECS`::
-	Setting this variable to `1` will cause Git to treat all
+	Setting this Boolean environment variable to true will cause Git to treat all
 	pathspecs literally, rather than as glob patterns. For example,
 	running `GIT_LITERAL_PATHSPECS=1 git log -- '*.c'` will search
 	for commits that touch the path `*.c`, not any paths that the
@@ -865,15 +876,15 @@ for full details.
 	`git ls-tree`, `--raw` diff output, etc).
 
 `GIT_GLOB_PATHSPECS`::
-	Setting this variable to `1` will cause Git to treat all
+	Setting this Boolean environment variable to true will cause Git to treat all
 	pathspecs as glob patterns (aka "glob" magic).
 
 `GIT_NOGLOB_PATHSPECS`::
-	Setting this variable to `1` will cause Git to treat all
+	Setting this Boolean environment variable to true will cause Git to treat all
 	pathspecs as literal (aka "literal" magic).
 
 `GIT_ICASE_PATHSPECS`::
-	Setting this variable to `1` will cause Git to treat all
+	Setting this Boolean environment variable to true will cause Git to treat all
 	pathspecs as case-insensitive.
 
 `GIT_REFLOG_ACTION`::
@@ -887,7 +898,7 @@ for full details.
 	end user, to be recorded in the body of the reflog.
 
 `GIT_REF_PARANOIA`::
-	If set to `0`, ignore broken or badly named refs when iterating
+	If this Boolean environment variable is set to false, ignore broken or badly named refs when iterating
 	over lists of refs. Normally Git will try to include any such
 	refs, which may cause some operations to fail. This is usually
 	preferable, as potentially destructive operations (e.g.,
@@ -906,7 +917,7 @@ for full details.
 	`protocol.allow` in linkgit:git-config[1] for more details.
 
 `GIT_PROTOCOL_FROM_USER`::
-	Set to 0 to prevent protocols used by fetch/push/clone which are
+	Set this Boolean environment variable to false to prevent protocols used by fetch/push/clone which are
 	configured to the `user` state.  This is useful to restrict recursive
 	submodule initialization from an untrusted repository or for programs
 	which feed potentially-untrusted URLS to git commands.  See
@@ -934,7 +945,7 @@ only affects clones and fetches; it is not yet used for pushes (but may
 be in the future).
 
 `GIT_OPTIONAL_LOCKS`::
-	If set to `0`, Git will complete any requested operation without
+	If this Boolean environment variable is set to false, Git will complete any requested operation without
 	performing any optional sub-operations that require taking a lock.
 	For example, this will prevent `git status` from refreshing the
 	index as a side effect. This is useful for processes running in
diff --git a/howto/coordinate-embargoed-releases.html b/howto/coordinate-embargoed-releases.html
index 184dfe5b1..0a183adbd 100644
--- a/howto/coordinate-embargoed-releases.html
+++ b/howto/coordinate-embargoed-releases.html
@@ -873,7 +873,7 @@ Thanks,
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:30 PDT

+ 2022-10-10 14:40:52 PDT

 </div>

 </div>

 </body>

diff --git a/howto/keep-canonical-history-correct.html b/howto/keep-canonical-history-correct.html
index d032dff67..177292fe9 100644
--- a/howto/keep-canonical-history-correct.html
+++ b/howto/keep-canonical-history-correct.html
@@ -938,7 +938,7 @@ tip of your <em>master</em> again and redo the two merges:</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:30 PDT

+ 2022-10-10 14:40:52 PDT

 </div>

 </div>

 </body>

diff --git a/howto/maintain-git.html b/howto/maintain-git.html
index be766d4f0..1401d2d97 100644
--- a/howto/maintain-git.html
+++ b/howto/maintain-git.html
@@ -1469,7 +1469,7 @@ $ git update-ref -d $mf/ai/topic</code></pre>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:30 PDT

+ 2022-10-10 14:40:52 PDT

 </div>

 </div>

 </body>

diff --git a/howto/new-command.html b/howto/new-command.html
index 4d57fe413..e05e08963 100644
--- a/howto/new-command.html
+++ b/howto/new-command.html
@@ -863,7 +863,7 @@ letter [PATCH 0/n].
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:28 PDT

+ 2022-10-10 14:40:50 PDT

 </div>

 </div>

 </body>

diff --git a/howto/rebase-from-internal-branch.html b/howto/rebase-from-internal-branch.html
index 9d578ff8b..64f5cf4af 100644
--- a/howto/rebase-from-internal-branch.html
+++ b/howto/rebase-from-internal-branch.html
@@ -895,7 +895,7 @@ the #1' commit.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:30 PDT

+ 2022-10-10 14:40:52 PDT

 </div>

 </div>

 </body>

diff --git a/howto/rebuild-from-update-hook.html b/howto/rebuild-from-update-hook.html
index 2448a1b23..1f8f2b613 100644
--- a/howto/rebuild-from-update-hook.html
+++ b/howto/rebuild-from-update-hook.html
@@ -847,7 +847,7 @@ This is still crude and does not protect against simultaneous
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:30 PDT

+ 2022-10-10 14:40:52 PDT

 </div>

 </div>

 </body>

diff --git a/howto/recover-corrupted-blob-object.html b/howto/recover-corrupted-blob-object.html
index 9d3a93fbd..ff815c4b3 100644
--- a/howto/recover-corrupted-blob-object.html
+++ b/howto/recover-corrupted-blob-object.html
@@ -880,7 +880,7 @@ thing.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:30 PDT

+ 2022-10-10 14:40:52 PDT

 </div>

 </div>

 </body>

diff --git a/howto/recover-corrupted-object-harder.html b/howto/recover-corrupted-object-harder.html
index daecbfeba..3b2363f23 100644
--- a/howto/recover-corrupted-object-harder.html
+++ b/howto/recover-corrupted-object-harder.html
@@ -1189,7 +1189,7 @@ int main(int argc, char **argv)
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:30 PDT

+ 2022-10-10 14:40:52 PDT

 </div>

 </div>

 </body>

diff --git a/howto/revert-a-faulty-merge.html b/howto/revert-a-faulty-merge.html
index 28ab5b8ee..81c4f03ae 100644
--- a/howto/revert-a-faulty-merge.html
+++ b/howto/revert-a-faulty-merge.html
@@ -1025,7 +1025,7 @@ P---o---o---M---x---x---W---x---M2
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:29 PDT

+ 2022-10-10 14:40:52 PDT

 </div>

 </div>

 </body>

diff --git a/howto/revert-branch-rebase.html b/howto/revert-branch-rebase.html
index f9842b0df..c7d7dfba3 100644
--- a/howto/revert-branch-rebase.html
+++ b/howto/revert-branch-rebase.html
@@ -907,7 +907,7 @@ Committed merge 7fb9b7262a1d1e0a47bbfdcbbcf50ce0635d3f8f
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:28 PDT

+ 2022-10-10 14:40:50 PDT

 </div>

 </div>

 </body>

diff --git a/howto/separating-topic-branches.html b/howto/separating-topic-branches.html
index 4dcd17682..4fc76faaa 100644
--- a/howto/separating-topic-branches.html
+++ b/howto/separating-topic-branches.html
@@ -841,7 +841,7 @@ o---o"master"</code></pre>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:29 PDT

+ 2022-10-10 14:40:51 PDT

 </div>

 </div>

 </body>

diff --git a/howto/setup-git-server-over-http.html b/howto/setup-git-server-over-http.html
index 5d40f9e0b..ff1c4a18d 100644
--- a/howto/setup-git-server-over-http.html
+++ b/howto/setup-git-server-over-http.html
@@ -1071,7 +1071,7 @@ help diagnosing the problem, but removes security checks.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:29 PDT

+ 2022-10-10 14:40:51 PDT

 </div>

 </div>

 </body>

diff --git a/howto/update-hook-example.html b/howto/update-hook-example.html
index d5c683e7b..5a831fc09 100644
--- a/howto/update-hook-example.html
+++ b/howto/update-hook-example.html
@@ -930,7 +930,7 @@ that JC can make non-fast-forward pushes on it.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:29 PDT

+ 2022-10-10 14:40:51 PDT

 </div>

 </div>

 </body>

diff --git a/howto/use-git-daemon.html b/howto/use-git-daemon.html
index e81ae4bf9..d95774d70 100644
--- a/howto/use-git-daemon.html
+++ b/howto/use-git-daemon.html
@@ -791,7 +791,7 @@ a good practice to put the paths after a "--" separator.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:28 PDT

+ 2022-10-10 14:40:51 PDT

 </div>

 </div>

 </body>

diff --git a/howto/using-merge-subtree.html b/howto/using-merge-subtree.html
index 8b529bc14..649fe6a82 100644
--- a/howto/using-merge-subtree.html
+++ b/howto/using-merge-subtree.html
@@ -848,7 +848,7 @@ Please note that if the other project merges from you, then it will
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:28 PDT

+ 2022-10-10 14:40:50 PDT

 </div>

 </div>

 </body>

diff --git a/howto/using-signed-tag-in-pull-request.html b/howto/using-signed-tag-in-pull-request.html
index 7ffd44134..1fc5fe354 100644
--- a/howto/using-signed-tag-in-pull-request.html
+++ b/howto/using-signed-tag-in-pull-request.html
@@ -952,7 +952,7 @@ as part of the merge commit.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-07 18:29:28 PDT

+ 2022-10-10 14:40:51 PDT

 </div>

 </div>

 </body>