Autogenerated HTML docs for v2.29.0-rc1

27 files changed, 83 insertions, 75 deletions

diff --git a/RelNotes/2.29.0.txt b/RelNotes/2.29.0.txt
index 43d7296ef..06ba2f803 100644
--- a/RelNotes/2.29.0.txt
+++ b/RelNotes/2.29.0.txt
@@ -156,7 +156,7 @@ Performance, Internal Implementation, Development Support etc.
    barrier to adoption.
 
  * The final leg of SHA-256 transition plus doc updates.  Note that
-   there is no inter-operability between SHA-1 and SHA-256
+   there is no interoperability between SHA-1 and SHA-256
    repositories yet.
 
  * CMake support to build with MSVC for Windows bypassing the Makefile.
@@ -184,10 +184,6 @@ Performance, Internal Implementation, Development Support etc.
    the ref backend in use, as its format is much richer than the
    normal refs, and written directly by "git fetch" as a plain file..
 
- * A handful of places in in-tree code still relied on being able to
-   execute the git subcommands, especially built-ins, in "git-foo"
-   form, which have been corrected.
-
  * An unused binary has been discarded, and and a bunch of commands
    have been turned into into built-in.
 
@@ -216,10 +212,25 @@ Performance, Internal Implementation, Development Support etc.
  * "diff-highlight" (in contrib/) had a logic to flush its output upon
    seeing a blank line but the way it detected a blank line was broken.
 
+ * The logic to skip testing on the tagged commit and the tag itself
+   was not quite consistent which led to failure of Windows test
+   tasks.  It has been revamped to consistently skip revisions that
+   have already been tested, based on the tree object of the revision.
+
 
 Fixes since v2.28
 -----------------
 
+ * The "mediawiki" remote backend which lives in contrib/mw-to-git/
+   and is not built with git by default, had an RCE bug allowing a
+   malicious MediaWiki server operator to inject arbitrary commands
+   for execution by a cloning client. This has been fixed.
+
+   The bug was discovered and reported by Joern Schneeweisz of GitLab
+   to the git-security mailing list. Its practical impact due to the
+   obscurity of git-remote-mediawiki was deemed small enough to forgo
+   a dedicated security release.
+
  * "git clone --separate-git-dir=$elsewhere" used to stomp on the
    contents of the existing directory $elsewhere, which has been
    taught to fail when $elsewhere is not an empty directory.
@@ -355,16 +366,13 @@ Fixes since v2.28
    "git log --tags=no-tag-matches-this-pattern" does.
    (merge 04a0e98515 jk/rev-input-given-fix later to maint).
 
- * Various callers of run_command API has been modernized.
+ * Various callers of run_command API have been modernized.
    (merge afbdba391e jc/run-command-use-embedded-args later to maint).
 
  * List of options offered and accepted by "git add -i/-p" were
    inconsistent, which have been corrected.
    (merge ce910287e7 pw/add-p-allowed-options-fix later to maint).
 
- * Various callers of run_command API has been modernized.
-   (merge afbdba391e jc/run-command-use-embedded-args later to maint).
-
  * "git diff --stat -w" showed 0-line changes for paths whose changes
    were only whitespaces, which was not intuitive.  We now omit such
    paths from the stat output.
@@ -381,7 +389,7 @@ Fixes since v2.28
    information (e.g. "@{u}" does not record what branch the user was
    on hence which branch 'the upstream' needs to be computed, and even
    if the record were available, the relationship between branches may
-   have changed), at least hide the error to allow "status" show its
+   have changed), at least hide the error and allow "status" to show its
    output.
 
  * "git status --short" quoted a path with SP in it when tracked, but
@@ -398,7 +406,7 @@ Fixes since v2.28
    (merge 378fe5fc3d mt/config-fail-nongit-early later to maint).
 
  * There is a logic to estimate how many objects are in the
-   repository, which is mean to run once per process invocation, but
+   repository, which is meant to run once per process invocation, but
    it ran every time the estimated value was requested.
    (merge 67bb65de5d jk/dont-count-existing-objects-twice later to maint).
 
@@ -411,8 +419,8 @@ Fixes since v2.28
    which has been corrected.
    (merge 4e735c1326 ar/fetch-ipversion-in-all later to maint).
 
- * The "unshelve" subcommand of "git p4" used incorrectly used
-   commit^N where it meant to say commit~N to name the Nth generation
+ * The "unshelve" subcommand of "git p4" incorrectly used commit^N
+   where it meant to say commit~N to name the Nth generation
    ancestor, which has been corrected.
    (merge 0acbf5997f ld/p4-unshelve-fix later to maint).
 
diff --git a/SubmittingPatches.html b/SubmittingPatches.html
index 5e18b2fa6..bf87224b3 100644
--- a/SubmittingPatches.html
+++ b/SubmittingPatches.html
@@ -1389,7 +1389,7 @@ this problem around.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2020-10-05 15:18:07 PDT

+ 2020-10-09 08:48:16 PDT

 </div>

 </div>

 </body>

diff --git a/git-bisect-lk2009.html b/git-bisect-lk2009.html
index f27528fb8..f7f9901ef 100644
--- a/git-bisect-lk2009.html
+++ b/git-bisect-lk2009.html
@@ -1167,7 +1167,7 @@ and Z will be kept:</p></div>
 Z-Z</code></pre>

 </div></div>

 <div class="paragraph"><p>2) starting from the "good" ends of the graph, associate to each

-commit the number of ancestors it has plus one</p></div>

+   commit the number of ancestors it has plus one</p></div>

 <div class="paragraph"><p>For example with the following graph where H is the "bad" commit and A

 and D are some parents of some "good" commits:</p></div>

 <div class="listingblock">

@@ -1202,7 +1202,7 @@ A-B-C
 D---E</code></pre>

 </div></div>

 <div class="paragraph"><p>4) the best bisection point is the commit with the highest associated

-number</p></div>

+   number</p></div>

 <div class="paragraph"><p>So in the above example the best bisection point is commit C.</p></div>

 <div class="paragraph"><p>5) note that some shortcuts are implemented to speed up the algorithm</p></div>

 <div class="paragraph"><p>As we know N from the beginning, we know that min(X, N - X) can&#8217;t be

@@ -1257,8 +1257,8 @@ suppose that these commits being for example on a branch or near a
 good or a bad commit does not give more or less information).</p></div>

 <div class="paragraph"><p>Let&#8217;s also suppose that we have a cleaned up graph like one after step

 1) in the bisection algorithm above. This means that we can measure

-the information we get in terms of number of commit we can remove from

-the graph..</p></div>

+   the information we get in terms of number of commit we can remove

+   from the graph..</p></div>

 <div class="paragraph"><p>And let&#8217;s take a commit X in the graph.</p></div>

 <div class="paragraph"><p>If X is found to be "good", then we know that its ancestors are all

 "good", so we want to say that:</p></div>

@@ -1348,14 +1348,14 @@ the bisection algorithm is the same for step 1) to 3). But then we use
 roughly the following steps:</p></div>

 <div class="paragraph"><p>6) sort the commit by decreasing associated value</p></div>

 <div class="paragraph"><p>7) if the first commit has not been skipped, we can return it and stop

-here</p></div>

+   here</p></div>

 <div class="paragraph"><p>8) otherwise filter out all the skipped commits in the sorted list</p></div>

 <div class="paragraph"><p>9) use a pseudo random number generator (PRNG) to generate a random

-number between 0 and 1</p></div>

+   number between 0 and 1</p></div>

 <div class="paragraph"><p>10) multiply this random number with its square root to bias it toward

-0</p></div>

+    0</p></div>

 <div class="paragraph"><p>11) multiply the result by the number of commits in the filtered list

-to get an index into this list</p></div>

+    to get an index into this list</p></div>

 <div class="paragraph"><p>12) return the commit at the computed index</p></div>

 </div>

 <div class="sect2">

@@ -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-03-10 08:03:13 PDT

+ 2020-10-09 08:47:57 PDT

 </div>

 </div>

 </body>

diff --git a/git-bisect-lk2009.txt b/git-bisect-lk2009.txt
index 3ba49e85b..f3d9566c8 100644
--- a/git-bisect-lk2009.txt
+++ b/git-bisect-lk2009.txt
@@ -473,7 +473,7 @@ Z-Z
 -------------
 
 2) starting from the "good" ends of the graph, associate to each
-commit the number of ancestors it has plus one
+   commit the number of ancestors it has plus one
 
 For example with the following graph where H is the "bad" commit and A
 and D are some parents of some "good" commits:
@@ -514,7 +514,7 @@ D---E
 -------------
 
 4) the best bisection point is the commit with the highest associated
-number
+   number
 
 So in the above example the best bisection point is commit C.
 
@@ -580,8 +580,8 @@ good or a bad commit does not give more or less information).
 
 Let's also suppose that we have a cleaned up graph like one after step
 1) in the bisection algorithm above. This means that we can measure
-the information we get in terms of number of commit we can remove from
-the graph..
+   the information we get in terms of number of commit we can remove
+   from the graph..
 
 And let's take a commit X in the graph.
 
@@ -689,18 +689,18 @@ roughly the following steps:
 6) sort the commit by decreasing associated value
 
 7) if the first commit has not been skipped, we can return it and stop
-here
+   here
 
 8) otherwise filter out all the skipped commits in the sorted list
 
 9) use a pseudo random number generator (PRNG) to generate a random
-number between 0 and 1
+   number between 0 and 1
 
 10) multiply this random number with its square root to bias it toward
-0
+    0
 
 11) multiply the result by the number of commits in the filtered list
-to get an index into this list
+    to get an index into this list
 
 12) return the commit at the computed index
 
diff --git a/git-grep.html b/git-grep.html
index 46df49055..0667f2487 100644
--- a/git-grep.html
+++ b/git-grep.html
@@ -1157,7 +1157,7 @@ providing this option will cause it to die.</p></div>
         Use \0 as the delimiter for pathnames in the output, and print

         them verbatim. Without this option, pathnames with "unusual"

         characters are quoted as explained for the configuration

-        variable core.quotePath (see git-config(1)).

+        variable core.quotePath (see <a href="git-config.html">git-config(1)</a>).

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1467,7 +1467,7 @@ performance in this case, it might be desirable to use <code>--threads=1</code>.
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2020-04-29 14:18:27 PDT

+ 2020-10-09 08:47:57 PDT

 </div>

 </div>

 </body>

diff --git a/git-grep.txt b/git-grep.txt
index a7f9bc99e..6077ff01a 100644
--- a/git-grep.txt
+++ b/git-grep.txt
@@ -209,7 +209,7 @@ providing this option will cause it to die.
 	Use \0 as the delimiter for pathnames in the output, and print
 	them verbatim. Without this option, pathnames with "unusual"
 	characters are quoted as explained for the configuration
-	variable core.quotePath (see git-config(1)).
+	variable core.quotePath (see linkgit:git-config[1]).
 
 -o::
 --only-matching::
diff --git a/git-init.html b/git-init.html
index cf6a8629f..8d4d69355 100644
--- a/git-init.html
+++ b/git-init.html
@@ -837,7 +837,7 @@ repository.
 <div class="paragraph"><p>If this is reinitialization, the repository will be moved to the specified path.</p></div>

 </dd>

 <dt class="hdlist1">

--b &lt;branch-name

+-b &lt;branch-name&gt;

 </dt>

 <dt class="hdlist1">

 --initial-branch=&lt;branch-name&gt;

@@ -1000,7 +1000,7 @@ Record the pristine state as the first commit in the history.
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2020-08-24 15:54:20 PDT

+ 2020-10-09 08:47:57 PDT

 </div>

 </div>

 </body>

diff --git a/git-init.txt b/git-init.txt
index f35f70f13..59ecda6c1 100644
--- a/git-init.txt
+++ b/git-init.txt
@@ -70,7 +70,7 @@ repository.
 +
 If this is reinitialization, the repository will be moved to the specified path.
 
--b <branch-name::
+-b <branch-name>::
 --initial-branch=<branch-name>::
 
 Use the specified name for the initial branch in the newly created repository.
diff --git a/git-remote.html b/git-remote.html
index a750b5ce9..4ac27b926 100644
--- a/git-remote.html
+++ b/git-remote.html
@@ -750,7 +750,7 @@ git-remote(1) Manual Page
 <div class="sectionbody">

 <div class="verseblock">

 <pre class="content"><em>git remote</em> [-v | --verbose]

-<em>git remote add</em> [-t &lt;branch&gt;] [-m &lt;master&gt;] [-f] [--[no-]tags] [--mirror=&lt;fetch|push&gt;] &lt;name&gt; &lt;url&gt;

+<em>git remote add</em> [-t &lt;branch&gt;] [-m &lt;master&gt;] [-f] [--[no-]tags] [--mirror=(fetch|push)] &lt;name&gt; &lt;url&gt;

 <em>git remote rename</em> &lt;old&gt; &lt;new&gt;

 <em>git remote remove</em> &lt;name&gt;

 <em>git remote set-head</em> &lt;name&gt; (-a | --auto | -d | --delete | &lt;branch&gt;)

@@ -785,7 +785,7 @@ git-remote(1) Manual Page
 <dd>

 <p>

         Be a little more verbose and show remote url after name.

-        NOTE: This must be placed between <code>remote</code> and <code>subcommand</code>.

+        NOTE: This must be placed between <code>remote</code> and subcommand.

 </p>

 </dd>

 </dl></div>

@@ -802,7 +802,7 @@ subcommands are available to perform operations on the remotes.</p></div>
 </dt>

 <dd>

 <p>

-Adds a remote named &lt;name&gt; for the repository at

+Add a remote named &lt;name&gt; for the repository at

 &lt;url&gt;.  The command <code>git fetch &lt;name&gt;</code> can then be used to create and

 update remote-tracking branches &lt;name&gt;/&lt;branch&gt;.

 </p>

@@ -869,12 +869,12 @@ specify <code>origin/master</code>.
 <div class="paragraph"><p>With <code>-d</code> or <code>--delete</code>, the symbolic ref <code>refs/remotes/&lt;name&gt;/HEAD</code> is deleted.</p></div>

 <div class="paragraph"><p>With <code>-a</code> or <code>--auto</code>, the remote is queried to determine its <code>HEAD</code>, then the

 symbolic-ref <code>refs/remotes/&lt;name&gt;/HEAD</code> is set to the same branch. e.g., if the remote

-<code>HEAD</code> is pointed at <code>next</code>, "<code>git remote set-head origin -a</code>" will set

+<code>HEAD</code> is pointed at <code>next</code>, <code>git remote set-head origin -a</code> will set

 the symbolic-ref <code>refs/remotes/origin/HEAD</code> to <code>refs/remotes/origin/next</code>. This will

 only work if <code>refs/remotes/origin/next</code> already exists; if not it must be

 fetched first.</p></div>

-<div class="paragraph"><p>Use <code>&lt;branch&gt;</code> to set the symbolic-ref <code>refs/remotes/&lt;name&gt;/HEAD</code> explicitly. e.g., "git

-remote set-head origin master" will set the symbolic-ref <code>refs/remotes/origin/HEAD</code> to

+<div class="paragraph"><p>Use <code>&lt;branch&gt;</code> to set the symbolic-ref <code>refs/remotes/&lt;name&gt;/HEAD</code> explicitly. e.g., <code>git

+remote set-head origin master</code> will set the symbolic-ref <code>refs/remotes/origin/HEAD</code> to

 <code>refs/remotes/origin/master</code>. This will only work if

 <code>refs/remotes/origin/master</code> already exists; if not it must be fetched first.</p></div>

 </dd>

@@ -888,7 +888,7 @@ This can be used to track a subset of the available remote branches
 after the initial setup for a remote.

 </p>

 <div class="paragraph"><p>The named branches will be interpreted as if specified with the

-<code>-t</code> option on the <em>git remote add</em> command line.</p></div>

+<code>-t</code> option on the <code>git remote add</code> command line.</p></div>

 <div class="paragraph"><p>With <code>--add</code>, instead of replacing the list of currently tracked

 branches, adds to that list.</p></div>

 </dd>

@@ -947,7 +947,7 @@ fetch --prune &lt;name&gt;</code>, except that no new references will be fetched
 </p>

 <div class="paragraph"><p>See the PRUNING section of <a href="git-fetch.html">git-fetch(1)</a> for what it&#8217;ll prune

 depending on various configuration.</p></div>

-<div class="paragraph"><p>With <code>--dry-run</code> option, report what branches will be pruned, but do not

+<div class="paragraph"><p>With <code>--dry-run</code> option, report what branches would be pruned, but do not

 actually prune them.</p></div>

 </dd>

 <dt class="hdlist1">

@@ -956,10 +956,10 @@ actually prune them.</p></div>
 <dd>

 <p>

 Fetch updates for remotes or remote groups in the repository as defined by

-remotes.&lt;group&gt;.  If neither group nor remote is specified on the command line,

+<code>remotes.&lt;group&gt;</code>. If neither group nor remote is specified on the command line,

 the configuration parameter remotes.default will be used; if

 remotes.default is not defined, all remotes which do not have the

-configuration parameter remote.&lt;name&gt;.skipDefaultUpdate set to true will

+configuration parameter <code>remote.&lt;name&gt;.skipDefaultUpdate</code> set to true will

 be updated.  (See <a href="git-config.html">git-config(1)</a>).

 </p>

 <div class="paragraph"><p>With <code>--prune</code> option, run pruning against all the remotes that are updated.</p></div>

@@ -1045,7 +1045,7 @@ $ git merge origin</code></pre>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2020-03-10 08:03:13 PDT

+ 2020-10-09 08:47:57 PDT

 </div>

 </div>

 </body>

diff --git a/git-remote.txt b/git-remote.txt
index 9659abbf8..ea73386c8 100644
--- a/git-remote.txt
+++ b/git-remote.txt
@@ -10,7 +10,7 @@ SYNOPSIS
 --------
 [verse]
 'git remote' [-v | --verbose]
-'git remote add' [-t <branch>] [-m <master>] [-f] [--[no-]tags] [--mirror=<fetch|push>] <name> <url>
+'git remote add' [-t <branch>] [-m <master>] [-f] [--[no-]tags] [--mirror=(fetch|push)] <name> <url>
 'git remote rename' <old> <new>
 'git remote remove' <name>
 'git remote set-head' <name> (-a | --auto | -d | --delete | <branch>)
@@ -35,7 +35,7 @@ OPTIONS
 -v::
 --verbose::
 	Be a little more verbose and show remote url after name.
-	NOTE: This must be placed between `remote` and `subcommand`.
+	NOTE: This must be placed between `remote` and subcommand.
 
 
 COMMANDS
@@ -46,7 +46,7 @@ subcommands are available to perform operations on the remotes.
 
 'add'::
 
-Adds a remote named <name> for the repository at
+Add a remote named <name> for the repository at
 <url>.  The command `git fetch <name>` can then be used to create and
 update remote-tracking branches <name>/<branch>.
 +
@@ -109,13 +109,13 @@ With `-d` or `--delete`, the symbolic ref `refs/remotes/<name>/HEAD` is deleted.
 +
 With `-a` or `--auto`, the remote is queried to determine its `HEAD`, then the
 symbolic-ref `refs/remotes/<name>/HEAD` is set to the same branch. e.g., if the remote
-`HEAD` is pointed at `next`, "`git remote set-head origin -a`" will set
+`HEAD` is pointed at `next`, `git remote set-head origin -a` will set
 the symbolic-ref `refs/remotes/origin/HEAD` to `refs/remotes/origin/next`. This will
 only work if `refs/remotes/origin/next` already exists; if not it must be
 fetched first.
 +
-Use `<branch>` to set the symbolic-ref `refs/remotes/<name>/HEAD` explicitly. e.g., "git
-remote set-head origin master" will set the symbolic-ref `refs/remotes/origin/HEAD` to
+Use `<branch>` to set the symbolic-ref `refs/remotes/<name>/HEAD` explicitly. e.g., `git
+remote set-head origin master` will set the symbolic-ref `refs/remotes/origin/HEAD` to
 `refs/remotes/origin/master`. This will only work if
 `refs/remotes/origin/master` already exists; if not it must be fetched first.
 +
@@ -127,7 +127,7 @@ This can be used to track a subset of the available remote branches
 after the initial setup for a remote.
 +
 The named branches will be interpreted as if specified with the
-`-t` option on the 'git remote add' command line.
+`-t` option on the `git remote add` command line.
 +
 With `--add`, instead of replacing the list of currently tracked
 branches, adds to that list.
@@ -181,16 +181,16 @@ fetch --prune <name>`, except that no new references will be fetched.
 See the PRUNING section of linkgit:git-fetch[1] for what it'll prune
 depending on various configuration.
 +
-With `--dry-run` option, report what branches will be pruned, but do not
+With `--dry-run` option, report what branches would be pruned, but do not
 actually prune them.
 
 'update'::
 
 Fetch updates for remotes or remote groups in the repository as defined by
-remotes.<group>.  If neither group nor remote is specified on the command line,
+`remotes.<group>`. If neither group nor remote is specified on the command line,
 the configuration parameter remotes.default will be used; if
 remotes.default is not defined, all remotes which do not have the
-configuration parameter remote.<name>.skipDefaultUpdate set to true will
+configuration parameter `remote.<name>.skipDefaultUpdate` set to true will
 be updated.  (See linkgit:git-config[1]).
 +
 With `--prune` option, run pruning against all the remotes that are updated.
diff --git a/howto-index.html b/howto-index.html
index 2d4da839e..ebefe7e78 100644
--- a/howto-index.html
+++ b/howto-index.html
@@ -885,7 +885,7 @@ later validate it.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2020-10-05 15:18:00 PDT

+ 2020-10-09 08:48:09 PDT

 </div>

 </div>

 </body>

diff --git a/howto/keep-canonical-history-correct.html b/howto/keep-canonical-history-correct.html
index 4530a6280..fd3cfb0b7 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

- 2020-10-05 15:18:05 PDT

+ 2020-10-09 08:48:13 PDT

 </div>

 </div>

 </body>

diff --git a/howto/maintain-git.html b/howto/maintain-git.html
index 9025888c1..9b05d3f08 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

- 2020-10-05 15:18:05 PDT

+ 2020-10-09 08:48:14 PDT

 </div>

 </div>

 </body>

diff --git a/howto/new-command.html b/howto/new-command.html
index 2a4ae2bd1..d18fa8bb1 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

- 2020-10-05 15:18:02 PDT

+ 2020-10-09 08:48:10 PDT

 </div>

 </div>

 </body>

diff --git a/howto/rebase-from-internal-branch.html b/howto/rebase-from-internal-branch.html
index a24c6ae01..2a28a705c 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

- 2020-10-05 15:18:05 PDT

+ 2020-10-09 08:48:13 PDT

 </div>

 </div>

 </body>

diff --git a/howto/rebuild-from-update-hook.html b/howto/rebuild-from-update-hook.html
index 443535ae7..8f99fc57e 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

- 2020-10-05 15:18:04 PDT

+ 2020-10-09 08:48:13 PDT

 </div>

 </div>

 </body>

diff --git a/howto/recover-corrupted-blob-object.html b/howto/recover-corrupted-blob-object.html
index 8f82f2804..f974a6067 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

- 2020-10-05 15:18:04 PDT

+ 2020-10-09 08:48:13 PDT

 </div>

 </div>

 </body>

diff --git a/howto/recover-corrupted-object-harder.html b/howto/recover-corrupted-object-harder.html
index fb0856727..2749ca5a9 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

- 2020-10-05 15:18:04 PDT

+ 2020-10-09 08:48:13 PDT

 </div>

 </div>

 </body>

diff --git a/howto/revert-a-faulty-merge.html b/howto/revert-a-faulty-merge.html
index 9a72f2814..8eb42f211 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

- 2020-10-05 15:18:04 PDT

+ 2020-10-09 08:48:13 PDT

 </div>

 </div>

 </body>

diff --git a/howto/revert-branch-rebase.html b/howto/revert-branch-rebase.html
index 26f1b5022..e8fd29719 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

- 2020-10-05 15:18:02 PDT

+ 2020-10-09 08:48:11 PDT

 </div>

 </div>

 </body>

diff --git a/howto/separating-topic-branches.html b/howto/separating-topic-branches.html
index 1ec333134..e557b4abb 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

- 2020-10-05 15:18:04 PDT

+ 2020-10-09 08:48:12 PDT

 </div>

 </div>

 </body>

diff --git a/howto/setup-git-server-over-http.html b/howto/setup-git-server-over-http.html
index 25ad15946..2dd1c1a58 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

- 2020-10-05 15:18:03 PDT

+ 2020-10-09 08:48:12 PDT

 </div>

 </div>

 </body>

diff --git a/howto/update-hook-example.html b/howto/update-hook-example.html
index 53687ba07..4f8b5b65e 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

- 2020-10-05 15:18:03 PDT

+ 2020-10-09 08:48:12 PDT

 </div>

 </div>

 </body>

diff --git a/howto/use-git-daemon.html b/howto/use-git-daemon.html
index 4ef9d6fb7..97d7468c3 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

- 2020-10-05 15:18:03 PDT

+ 2020-10-09 08:48:12 PDT

 </div>

 </div>

 </body>

diff --git a/howto/using-merge-subtree.html b/howto/using-merge-subtree.html
index f0cd84c36..63b0ca88c 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

- 2020-10-05 15:18:02 PDT

+ 2020-10-09 08:48:11 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 af16e3e7b..020561db9 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

- 2020-10-05 15:18:02 PDT

+ 2020-10-09 08:48:11 PDT

 </div>

 </div>

 </body>

diff --git a/technical/api-index.html b/technical/api-index.html
index 71e60e917..4db76e478 100644
--- a/technical/api-index.html
+++ b/technical/api-index.html
@@ -770,7 +770,7 @@ documents them.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2020-10-05 15:18:11 PDT

+ 2020-10-09 08:48:20 PDT

 </div>

 </div>

 </body>