Autogenerated HTML docs for v2.39.0-rc0

36 files changed, 179 insertions, 75 deletions

diff --git a/RelNotes/2.39.0.txt b/RelNotes/2.39.0.txt
index 153bf6d89..bea9260cd 100644
--- a/RelNotes/2.39.0.txt
+++ b/RelNotes/2.39.0.txt
@@ -35,6 +35,29 @@ UI, Workflows & Features
  * "git repack" learns to send cruft objects out of the way into
    packfiles outside the repository.
 
+ * 'scalar reconfigure -a' is taught to automatically remove
+   scalar.repo entires which no longer exist.
+
+ * Redact headers from cURL's h2h3 module in GIT_CURL_VERBOSE and
+   others.
+
+ * 'git maintenance register' is taught to write configuration to an
+   arbitrary path, and 'git for-each-repo' is taught to expand tilde
+   characters in paths.
+
+ * When creating new notes, the template used to get a stray empty
+   newline, which has been removed.
+
+ * "git receive-pack" used to use all the local refs as the boundary for
+   checking connectivity of the data "git push" sent, but now it uses
+   only the refs that it advertised to the pusher. In a repository with
+   the .hideRefs configuration, this reduces the resources needed to
+   perform the check.
+
+ * With '--recurse-submodules=on-demand', all submodules are
+   recursively pushed.
+
+
 Performance, Internal Implementation, Development Support etc.
 --------------------------------------------------------------
 
@@ -124,6 +147,13 @@ Performance, Internal Implementation, Development Support etc.
  * A design document for sparse-checkout's future directions has been
    added.
 
+ * Teach chainlint.pl to annotate the original test definition instead
+   of the token stream.
+
+ * "make coccicheck" is time consuming. It has been made to run more
+   incrementally.
+
+
 Fixes since v2.38
 -----------------
 
@@ -271,6 +301,13 @@ Fixes since v2.38
    `update-ref` commands in the sequencer were removed, which has been
    corrected.
 
+ * Fix a regression in the bisect-helper which mistakenly treats
+   arguments to the command given to 'git bisect run' as arguments to
+   the helper.
+
+ * Correct an error where `git rebase` would mistakenly use a branch or
+   tag named "refs/rewritten/xyz" when missing a rebase label.
+
  * Other code cleanup, docfix, build fix, etc.
    (merge 413bc6d20a ds/cmd-main-reorder later to maint).
    (merge 8d2863e4ed nw/t1002-cleanup later to maint).
diff --git a/SubmittingPatches.html b/SubmittingPatches.html
index b5d9ddae4..7d20e7811 100644
--- a/SubmittingPatches.html
+++ b/SubmittingPatches.html
@@ -1446,7 +1446,7 @@ this problem around.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-18 07:23:35 JST

+ 2022-11-23 12:59:20 JST

 </div>

 </div>

 </body>

diff --git a/git-bisect-lk2009.html b/git-bisect-lk2009.html
index ddbbfe4f7..546f4b4e8 100644
--- a/git-bisect-lk2009.html
+++ b/git-bisect-lk2009.html
@@ -1983,7 +1983,7 @@ author to given a talk and for publishing this paper.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2020-10-18 13:46:42 PDT

+ 2020-10-19 05:46:42 JST

 </div>

 </div>

 </body>

diff --git a/git-config.html b/git-config.html
index 95dd88f29..3725fb649 100644
--- a/git-config.html
+++ b/git-config.html
@@ -9337,18 +9337,8 @@ push.recurseSubmodules
 </dt>

 <dd>

 <p>

-        Make sure all submodule commits used by the revisions to be pushed

-        are available on a remote-tracking branch. If the value is <em>check</em>

-        then Git will verify that all submodule commits that changed in the

-        revisions to be pushed are available on at least one remote of the

-        submodule. If any commits are missing, the push will be aborted and

-        exit with non-zero status. If the value is <em>on-demand</em> then all

-        submodules that changed in the revisions to be pushed will be

-        pushed. If on-demand was not able to push all necessary revisions

-        it will also be aborted and exit with non-zero status. If the value

-        is <em>no</em> then default behavior of ignoring submodules when pushing

-        is retained. You may override this configuration at time of push by

-        specifying <em>--recurse-submodules=check|on-demand|no</em>.

+        May be "check", "on-demand", "only", or "no", with the same behavior

+        as that of "push --recurse-submodules".

         If not set, <em>no</em> is used by default, unless <em>submodule.recurse</em> is

         set (in which case a <em>true</em> value means <em>on-demand</em>).

 </p>

diff --git a/git-log.html b/git-log.html
index 57d0b4ef2..3c0e93a3f 100644
--- a/git-log.html
+++ b/git-log.html
@@ -1334,6 +1334,18 @@ or <code>--all</code>. If a trailing <em>/&#42;</em> is intended, it must be giv
 explicitly.</p></div>

 </dd>

 <dt class="hdlist1">

+--exclude-hidden=[receive|uploadpack]

+</dt>

+<dd>

+<p>

+        Do not include refs that would be hidden by <code>git-receive-pack</code> or

+        <code>git-upload-pack</code> by consulting the appropriate <code>receive.hideRefs</code> or

+        <code>uploadpack.hideRefs</code> configuration along with <code>transfer.hideRefs</code> (see

+        <a href="git-config.html">git-config(1)</a>). This option affects the next pseudo-ref option

+        <code>--all</code> or <code>--glob</code> and is cleared after processing them.

+</p>

+</dd>

+<dt class="hdlist1">

 --reflog

 </dt>

 <dd>

diff --git a/git-maintenance.html b/git-maintenance.html
index 156864ebd..0be8fd58a 100644
--- a/git-maintenance.html
+++ b/git-maintenance.html
@@ -812,13 +812,13 @@ register
 </dt>

 <dd>

 <p>

-        Initialize Git config values so any scheduled maintenance will

-        start running on this repository. This adds the repository to the

-        <code>maintenance.repo</code> config variable in the current user&#8217;s global

-        config and enables some recommended configuration values for

-        <code>maintenance.&lt;task&gt;.schedule</code>. The tasks that are enabled are safe

-        for running in the background without disrupting foreground

-        processes.

+        Initialize Git config values so any scheduled maintenance will start

+        running on this repository. This adds the repository to the

+        <code>maintenance.repo</code> config variable in the current user&#8217;s global config,

+        or the config specified by --config-file option, and enables some

+        recommended configuration values for <code>maintenance.&lt;task&gt;.schedule</code>. The

+        tasks that are enabled are safe for running in the background without

+        disrupting foreground processes.

 </p>

 <div class="paragraph"><p>The <code>register</code> subcommand will also set the <code>maintenance.strategy</code> config

 value to <code>incremental</code>, if this value is not previously set. The

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

 <div id="footer-text">

 Last updated

- 2022-10-11 06:40:17 JST

+ 2022-11-23 12:59:10 JST

 </div>

 </div>

 </body>

diff --git a/git-maintenance.txt b/git-maintenance.txt
index bb888690e..805e5a2e3 100644
--- a/git-maintenance.txt
+++ b/git-maintenance.txt
@@ -50,13 +50,13 @@ stop::
 	the background maintenance is restarted later.
 
 register::
-	Initialize Git config values so any scheduled maintenance will
-	start running on this repository. This adds the repository to the
-	`maintenance.repo` config variable in the current user's global
-	config and enables some recommended configuration values for
-	`maintenance.<task>.schedule`. The tasks that are enabled are safe
-	for running in the background without disrupting foreground
-	processes.
+	Initialize Git config values so any scheduled maintenance will start
+	running on this repository. This adds the repository to the
+	`maintenance.repo` config variable in the current user's global config,
+	or the config specified by --config-file option, and enables some
+	recommended configuration values for `maintenance.<task>.schedule`. The
+	tasks that are enabled are safe for running in the background without
+	disrupting foreground processes.
 +
 The `register` subcommand will also set the `maintenance.strategy` config
 value to `incremental`, if this value is not previously set. The
diff --git a/git-push.html b/git-push.html
index 8def1a6ac..aa5eac5cb 100644
--- a/git-push.html
+++ b/git-push.html
@@ -1277,11 +1277,14 @@ a "no-op".</p></div>
         all submodules that changed in the revisions to be pushed will be

         pushed. If on-demand was not able to push all necessary revisions it will

         also be aborted and exit with non-zero status. If <em>only</em> is used all

-        submodules will be recursively pushed while the superproject is left

+        submodules will be pushed while the superproject is left

         unpushed. A value of <em>no</em> or using <code>--no-recurse-submodules</code> can be used

         to override the push.recurseSubmodules configuration variable when no

         submodule recursion is required.

 </p>

+<div class="paragraph"><p>When using <em>on-demand</em> or <em>only</em>, if a submodule has a

+"push.recurseSubmodules={on-demand,only}" or "submodule.recurse" configuration,

+further recursion will occur. In this case, "only" is treated as "on-demand".</p></div>

 </dd>

 <dt class="hdlist1">

 --[no-]verify

@@ -2120,18 +2123,8 @@ push.recurseSubmodules
 </dt>

 <dd>

 <p>

-        Make sure all submodule commits used by the revisions to be pushed

-        are available on a remote-tracking branch. If the value is <em>check</em>

-        then Git will verify that all submodule commits that changed in the

-        revisions to be pushed are available on at least one remote of the

-        submodule. If any commits are missing, the push will be aborted and

-        exit with non-zero status. If the value is <em>on-demand</em> then all

-        submodules that changed in the revisions to be pushed will be

-        pushed. If on-demand was not able to push all necessary revisions

-        it will also be aborted and exit with non-zero status. If the value

-        is <em>no</em> then default behavior of ignoring submodules when pushing

-        is retained. You may override this configuration at time of push by

-        specifying <em>--recurse-submodules=check|on-demand|no</em>.

+        May be "check", "on-demand", "only", or "no", with the same behavior

+        as that of "push --recurse-submodules".

         If not set, <em>no</em> is used by default, unless <em>submodule.recurse</em> is

         set (in which case a <em>true</em> value means <em>on-demand</em>).

 </p>

@@ -2183,7 +2176,7 @@ push.useBitmaps
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-09-15 05:23:11 JST

+ 2022-11-23 12:59:10 JST

 </div>

 </div>

 </body>

diff --git a/git-push.txt b/git-push.txt
index def7657ef..5bb1d5aae 100644
--- a/git-push.txt
+++ b/git-push.txt
@@ -409,10 +409,14 @@ Specifying `--no-force-if-includes` disables this behavior.
 	all submodules that changed in the revisions to be pushed will be
 	pushed. If on-demand was not able to push all necessary revisions it will
 	also be aborted and exit with non-zero status. If 'only' is used all
-	submodules will be recursively pushed while the superproject is left
+	submodules will be pushed while the superproject is left
 	unpushed. A value of 'no' or using `--no-recurse-submodules` can be used
 	to override the push.recurseSubmodules configuration variable when no
 	submodule recursion is required.
++
+When using 'on-demand' or 'only', if a submodule has a
+"push.recurseSubmodules={on-demand,only}" or "submodule.recurse" configuration,
+further recursion will occur. In this case, "only" is treated as "on-demand".
 
 --[no-]verify::
 	Toggle the pre-push hook (see linkgit:githooks[5]).  The
diff --git a/git-rev-list.html b/git-rev-list.html
index 83a257ffe..9fe84d83f 100644
--- a/git-rev-list.html
+++ b/git-rev-list.html
@@ -1150,6 +1150,18 @@ or <code>--all</code>. If a trailing <em>/&#42;</em> is intended, it must be giv
 explicitly.</p></div>

 </dd>

 <dt class="hdlist1">

+--exclude-hidden=[receive|uploadpack]

+</dt>

+<dd>

+<p>

+        Do not include refs that would be hidden by <code>git-receive-pack</code> or

+        <code>git-upload-pack</code> by consulting the appropriate <code>receive.hideRefs</code> or

+        <code>uploadpack.hideRefs</code> configuration along with <code>transfer.hideRefs</code> (see

+        <a href="git-config.html">git-config(1)</a>). This option affects the next pseudo-ref option

+        <code>--all</code> or <code>--glob</code> and is cleared after processing them.

+</p>

+</dd>

+<dt class="hdlist1">

 --reflog

 </dt>

 <dd>

diff --git a/git-rev-parse.html b/git-rev-parse.html
index 2b55c319e..1b0b323f8 100644
--- a/git-rev-parse.html
+++ b/git-rev-parse.html
@@ -1064,6 +1064,18 @@ or <code>--all</code>. If a trailing <em>/&#42;</em> is intended, it must be giv
 explicitly.</p></div>

 </dd>

 <dt class="hdlist1">

+--exclude-hidden=[receive|uploadpack]

+</dt>

+<dd>

+<p>

+        Do not include refs that would be hidden by <code>git-receive-pack</code> or

+        <code>git-upload-pack</code> by consulting the appropriate <code>receive.hideRefs</code> or

+        <code>uploadpack.hideRefs</code> configuration along with <code>transfer.hideRefs</code> (see

+        <a href="git-config.html">git-config(1)</a>). This option affects the next pseudo-ref option

+        <code>--all</code> or <code>--glob</code> and is cleared after processing them.

+</p>

+</dd>

+<dt class="hdlist1">

 --disambiguate=&lt;prefix&gt;

 </dt>

 <dd>

@@ -2063,7 +2075,7 @@ Similar to above:
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2021-01-26 11:03:13 JST

+ 2022-11-23 12:59:10 JST

 </div>

 </div>

 </body>

diff --git a/git-rev-parse.txt b/git-rev-parse.txt
index 6b8ca085a..bcd806928 100644
--- a/git-rev-parse.txt
+++ b/git-rev-parse.txt
@@ -197,6 +197,13 @@ respectively, and they must begin with `refs/` when applied to `--glob`
 or `--all`. If a trailing '/{asterisk}' is intended, it must be given
 explicitly.
 
+--exclude-hidden=[receive|uploadpack]::
+	Do not include refs that would be hidden by `git-receive-pack` or
+	`git-upload-pack` by consulting the appropriate `receive.hideRefs` or
+	`uploadpack.hideRefs` configuration along with `transfer.hideRefs` (see
+	linkgit:git-config[1]). This option affects the next pseudo-ref option
+	`--all` or `--glob` and is cleared after processing them.
+
 --disambiguate=<prefix>::
 	Show every object whose name begins with the given prefix.
 	The <prefix> must be at least 4 hexadecimal digits long to
diff --git a/git-shortlog.html b/git-shortlog.html
index 4d8bfb180..f8cdb3038 100644
--- a/git-shortlog.html
+++ b/git-shortlog.html
@@ -1273,6 +1273,18 @@ or <code>--all</code>. If a trailing <em>/&#42;</em> is intended, it must be giv
 explicitly.</p></div>

 </dd>

 <dt class="hdlist1">

+--exclude-hidden=[receive|uploadpack]

+</dt>

+<dd>

+<p>

+        Do not include refs that would be hidden by <code>git-receive-pack</code> or

+        <code>git-upload-pack</code> by consulting the appropriate <code>receive.hideRefs</code> or

+        <code>uploadpack.hideRefs</code> configuration along with <code>transfer.hideRefs</code> (see

+        <a href="git-config.html">git-config(1)</a>). This option affects the next pseudo-ref option

+        <code>--all</code> or <code>--glob</code> and is cleared after processing them.

+</p>

+</dd>

+<dt class="hdlist1">

 --reflog

 </dt>

 <dd>

diff --git a/git-tools.html b/git-tools.html
index bedfaae59..2a55ada25 100644
--- a/git-tools.html
+++ b/git-tools.html
@@ -752,7 +752,7 @@ more efficiently, so this manually-maintained list has been retired.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2020-03-10 15:02:33 PDT

+ 2020-03-11 07:02:33 JST

 </div>

 </div>

 </body>

diff --git a/gitcredentials.html b/gitcredentials.html
index 71737cd8a..5dcd34c50 100644
--- a/gitcredentials.html
+++ b/gitcredentials.html
@@ -827,7 +827,9 @@ for a password. It is generally configured by adding this to your config:</p></d
 </div></div>

 <div class="paragraph"><p>Credential helpers, on the other hand, are external programs from which Git can

 request both usernames and passwords; they typically interface with secure

-storage provided by the OS or other programs.</p></div>

+storage provided by the OS or other programs. Alternatively, a

+credential-generating helper might generate credentials for certain servers via

+some API.</p></div>

 <div class="paragraph"><p>To use a helper, you must first select one to use. Git currently

 includes the following helpers:</p></div>

 <div class="dlist"><dl>

@@ -1090,8 +1092,8 @@ password had been provided.</p></div>
 <div class="paragraph"><p>For a <code>store</code> or <code>erase</code> operation, the helper&#8217;s output is ignored.</p></div>

 <div class="paragraph"><p>If a helper fails to perform the requested operation or needs to notify

 the user of a potential issue, it may write to stderr.</p></div>

-<div class="paragraph"><p>If it does not support the requested operation (e.g., a read-only store),

-it should silently ignore the request.</p></div>

+<div class="paragraph"><p>If it does not support the requested operation (e.g., a read-only store

+or generator), it should silently ignore the request.</p></div>

 <div class="paragraph"><p>If a helper receives any other operation, it should silently ignore the

 request. This leaves room for future operations to be added (older

 helpers will just ignore the new requests).</p></div>

@@ -1108,7 +1110,7 @@ helpers will just ignore the new requests).</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-11-21 15:53:16 JST

+ 2022-11-23 12:59:10 JST

 </div>

 </div>

 </body>

diff --git a/gitcredentials.txt b/gitcredentials.txt
index d6665d2f3..4522471c3 100644
--- a/gitcredentials.txt
+++ b/gitcredentials.txt
@@ -62,7 +62,9 @@ for a password. It is generally configured by adding this to your config:
 
 Credential helpers, on the other hand, are external programs from which Git can
 request both usernames and passwords; they typically interface with secure
-storage provided by the OS or other programs.
+storage provided by the OS or other programs. Alternatively, a
+credential-generating helper might generate credentials for certain servers via
+some API.
 
 To use a helper, you must first select one to use. Git currently
 includes the following helpers:
@@ -288,8 +290,8 @@ For a `store` or `erase` operation, the helper's output is ignored.
 If a helper fails to perform the requested operation or needs to notify
 the user of a potential issue, it may write to stderr.
 
-If it does not support the requested operation (e.g., a read-only store),
-it should silently ignore the request.
+If it does not support the requested operation (e.g., a read-only store
+or generator), it should silently ignore the request.
 
 If a helper receives any other operation, it should silently ignore the
 request. This leaves room for future operations to be added (older
diff --git a/howto-index.html b/howto-index.html
index fce1f88c4..1ce8b91b1 100644
--- a/howto-index.html
+++ b/howto-index.html
@@ -895,7 +895,7 @@ later validate it.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-11-11 23:55:31 PST

+ 2022-11-23 12:59:14 JST

 </div>

 </div>

 </body>

diff --git a/howto/coordinate-embargoed-releases.html b/howto/coordinate-embargoed-releases.html
index df45d31e8..227aff4b7 100644
--- a/howto/coordinate-embargoed-releases.html
+++ b/howto/coordinate-embargoed-releases.html
@@ -1038,7 +1038,7 @@ Thanks,
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-11-21 15:53:49 JST

+ 2022-11-23 12:59:18 JST

 </div>

 </div>

 </body>

diff --git a/howto/keep-canonical-history-correct.html b/howto/keep-canonical-history-correct.html
index 5d37ed8d5..6e517dd77 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-11-21 15:53:49 JST

+ 2022-11-23 12:59:18 JST

 </div>

 </div>

 </body>

diff --git a/howto/maintain-git.html b/howto/maintain-git.html
index 283a192c3..8359bc5f5 100644
--- a/howto/maintain-git.html
+++ b/howto/maintain-git.html
@@ -1103,7 +1103,7 @@ Prepare <em>jch</em> branch, which is used to represent somewhere
 </p>

 <div class="literalblock">

 <div class="content">

-<pre><code>$ Meta/Reintegrate master..seen &gt;Meta/redo-jch.sh</code></pre>

+<pre><code>$ Meta/Reintegrate master..jch &gt;Meta/redo-jch.sh</code></pre>

 </div></div>

 <div class="literalblock">

 <div class="content">

@@ -1189,6 +1189,15 @@ and rectified.</code></pre>
 </div></div>

 <div class="literalblock">

 <div class="content">

+<pre><code>Then build the rest of 'jch':</code></pre>

+</div></div>

+<div class="literalblock">

+<div class="content">

+<pre><code>$ git checkout jch

+$ sh Meta/redo-jch.sh</code></pre>

+</div></div>

+<div class="literalblock">

+<div class="content">

 <pre><code>When all is well, clean up the redo-jch.sh script with</code></pre>

 </div></div>

 <div class="literalblock">

@@ -1208,7 +1217,7 @@ Rebuild <em>seen</em>.
 </p>

 <div class="literalblock">

 <div class="content">

-<pre><code>$ Meta/Reintegrate master..seen &gt;Meta/redo-seen.sh</code></pre>

+<pre><code>$ Meta/Reintegrate jch..seen &gt;Meta/redo-seen.sh</code></pre>

 </div></div>

 <div class="literalblock">

 <div class="content">

@@ -1469,7 +1478,7 @@ $ git update-ref -d $mf/ai/topic</code></pre>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-11-21 15:53:49 JST

+ 2022-11-23 12:59:18 JST

 </div>

 </div>

 </body>

diff --git a/howto/maintain-git.txt b/howto/maintain-git.txt
index 215e2edb0..d07c6d44e 100644
--- a/howto/maintain-git.txt
+++ b/howto/maintain-git.txt
@@ -231,7 +231,7 @@ by doing the following:
  - Prepare 'jch' branch, which is used to represent somewhere
    between 'master' and 'seen' and often is slightly ahead of 'next'.
 
-     $ Meta/Reintegrate master..seen >Meta/redo-jch.sh
+     $ Meta/Reintegrate master..jch >Meta/redo-jch.sh
 
    The result is a script that lists topics to be merged in order to
    rebuild 'seen' as the input to Meta/Reintegrate script.  Remove
@@ -283,6 +283,11 @@ by doing the following:
 
      $ git diff jch next
 
+   Then build the rest of 'jch':
+
+     $ git checkout jch
+     $ sh Meta/redo-jch.sh
+
    When all is well, clean up the redo-jch.sh script with
 
      $ sh Meta/redo-jch.sh -u
@@ -293,7 +298,7 @@ by doing the following:
 
  - Rebuild 'seen'.
 
-     $ Meta/Reintegrate master..seen >Meta/redo-seen.sh
+     $ Meta/Reintegrate jch..seen >Meta/redo-seen.sh
 
    Edit the result by adding new topics that are not still in 'seen'
    in the script.  Then
diff --git a/howto/new-command.html b/howto/new-command.html
index 47a0bf388..8ba53752d 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-11-21 15:53:47 JST

+ 2022-11-23 12:59:15 JST

 </div>

 </div>

 </body>

diff --git a/howto/rebase-from-internal-branch.html b/howto/rebase-from-internal-branch.html
index ff382b4e9..63157b9f9 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-11-21 15:53:49 JST

+ 2022-11-23 12:59:18 JST

 </div>

 </div>

 </body>

diff --git a/howto/rebuild-from-update-hook.html b/howto/rebuild-from-update-hook.html
index bc3026a1d..4510123a2 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-11-21 15:53:49 JST

+ 2022-11-23 12:59:18 JST

 </div>

 </div>

 </body>

diff --git a/howto/recover-corrupted-blob-object.html b/howto/recover-corrupted-blob-object.html
index 0ca3d8e3f..42ab5e55a 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-11-21 15:53:49 JST

+ 2022-11-23 12:59:17 JST

 </div>

 </div>

 </body>

diff --git a/howto/recover-corrupted-object-harder.html b/howto/recover-corrupted-object-harder.html
index 16ba0b283..9f39c25dc 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-11-21 15:53:49 JST

+ 2022-11-23 12:59:18 JST

 </div>

 </div>

 </body>

diff --git a/howto/revert-a-faulty-merge.html b/howto/revert-a-faulty-merge.html
index f55dc1daa..7217a56b9 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-11-21 15:53:48 JST

+ 2022-11-23 12:59:17 JST

 </div>

 </div>

 </body>

diff --git a/howto/revert-branch-rebase.html b/howto/revert-branch-rebase.html
index 6287c564c..bdcbbe87c 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-11-21 15:53:47 JST

+ 2022-11-23 12:59:15 JST

 </div>

 </div>

 </body>

diff --git a/howto/separating-topic-branches.html b/howto/separating-topic-branches.html
index 0c83c9cba..f9f9aa51a 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-11-21 15:53:48 JST

+ 2022-11-23 12:59:17 JST

 </div>

 </div>

 </body>

diff --git a/howto/setup-git-server-over-http.html b/howto/setup-git-server-over-http.html
index 3e9b0bfbd..fb05394e8 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-11-21 15:53:48 JST

+ 2022-11-23 12:59:17 JST

 </div>

 </div>

 </body>

diff --git a/howto/update-hook-example.html b/howto/update-hook-example.html
index 464447fea..294095265 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-11-21 15:53:48 JST

+ 2022-11-23 12:59:16 JST

 </div>

 </div>

 </body>

diff --git a/howto/use-git-daemon.html b/howto/use-git-daemon.html
index 4676ce398..8b7dda1e2 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-11-21 15:53:48 JST

+ 2022-11-23 12:59:16 JST

 </div>

 </div>

 </body>

diff --git a/howto/using-merge-subtree.html b/howto/using-merge-subtree.html
index bcf66b068..982df97d4 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-11-21 15:53:47 JST

+ 2022-11-23 12:59:15 JST

 </div>

 </div>

 </body>

diff --git a/howto/using-signed-tag-in-pull-request.html b/howto/using-signed-tag-in-pull-request.html
index 948a49380..aaec335c2 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-11-21 15:53:47 JST

+ 2022-11-23 12:59:16 JST

 </div>

 </div>

 </body>

diff --git a/rev-list-options.txt b/rev-list-options.txt
index 183750956..ff68e4840 100644
--- a/rev-list-options.txt
+++ b/rev-list-options.txt
@@ -195,6 +195,13 @@ respectively, and they must begin with `refs/` when applied to `--glob`
 or `--all`. If a trailing '/{asterisk}' is intended, it must be given
 explicitly.
 
+--exclude-hidden=[receive|uploadpack]::
+	Do not include refs that would be hidden by `git-receive-pack` or
+	`git-upload-pack` by consulting the appropriate `receive.hideRefs` or
+	`uploadpack.hideRefs` configuration along with `transfer.hideRefs` (see
+	linkgit:git-config[1]). This option affects the next pseudo-ref option
+	`--all` or `--glob` and is cleared after processing them.
+
 --reflog::
 	Pretend as if all objects mentioned by reflogs are listed on the
 	command line as `<commit>`.
diff --git a/technical/api-index.html b/technical/api-index.html
index ece065f38..c6fd78a58 100644
--- a/technical/api-index.html
+++ b/technical/api-index.html
@@ -775,7 +775,7 @@ documents them.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-10-04 01:55:20 JST

+ 2022-11-23 12:59:22 JST

 </div>

 </div>

 </body>