Autogenerated HTML docs for v2.34.1-428-gdcc0c

21 files changed, 151 insertions, 117 deletions

diff --git a/RelNotes/2.35.0.txt b/RelNotes/2.35.0.txt
index dc72843e1..aa311cb96 100644
--- a/RelNotes/2.35.0.txt
+++ b/RelNotes/2.35.0.txt
@@ -62,6 +62,9 @@ UI, Workflows & Features
    with the "--allow-empty" option.  It also learned to honor the
    "--quiet" option given from the command line.
 
+ * The "init" and "set" subcommands in "git sparse-checkout" have been
+   unified for a better user experience and performance.
+
 
 Performance, Internal Implementation, Development Support etc.
 
@@ -130,6 +133,14 @@ Performance, Internal Implementation, Development Support etc.
 
  * The DEVELOPER=yes build uses -std=gnu99 now.
 
+ * "git format-patch" uses a single rev_info instance and then exits.
+   Mark the structure with UNLEAK() macro to squelch leak sanitizer.
+
+ * New interface into the tmp-objdir API to help in-core use of the
+   quarantine feature.
+
+ * Broken &&-chains in the test scripts have been corrected.
+
 
 Fixes since v2.34
 -----------------
diff --git a/git-clone.html b/git-clone.html
index b3898db44..56195268a 100644
--- a/git-clone.html
+++ b/git-clone.html
@@ -978,10 +978,10 @@ objects from the source repository into a pack in the cloned repository.</p></di
 </dt>

 <dd>

 <p>

-        Initialize the sparse-checkout file so the working

-        directory starts with only the files in the root

-        of the repository. The sparse-checkout file can be

-        modified to grow the working directory as needed.

+        Employ a sparse-checkout, with only files in the toplevel

+        directory initially being present.  The

+        <a href="git-sparse-checkout.html">git-sparse-checkout(1)</a> command can be used to grow the

+        working directory as needed.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1430,7 +1430,7 @@ Create a bare repository to publish your changes to the public:
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2021-12-10 14:52:02 PST

+ 2022-01-03 16:49:08 PST

 </div>

 </div>

 </body>

diff --git a/git-clone.txt b/git-clone.txt
index 9685ea069..984d19493 100644
--- a/git-clone.txt
+++ b/git-clone.txt
@@ -167,10 +167,10 @@ objects from the source repository into a pack in the cloned repository.
 	configuration variables are created.
 
 --sparse::
-	Initialize the sparse-checkout file so the working
-	directory starts with only the files in the root
-	of the repository. The sparse-checkout file can be
-	modified to grow the working directory as needed.
+	Employ a sparse-checkout, with only files in the toplevel
+	directory initially being present.  The
+	linkgit:git-sparse-checkout[1] command can be used to grow the
+	working directory as needed.
 
 --filter=<filter-spec>::
 	Use the partial clone feature and request that the server sends
diff --git a/git-sparse-checkout.html b/git-sparse-checkout.html
index cc6ee4a2a..084a8ac87 100644
--- a/git-sparse-checkout.html
+++ b/git-sparse-checkout.html
@@ -777,29 +777,37 @@ THE FUTURE.</p></div>
 </p>

 </dd>

 <dt class="hdlist1">

-<em>init</em>

+<em>set</em>

 </dt>

 <dd>

 <p>

-        Enable the <code>core.sparseCheckout</code> setting. If the

-        sparse-checkout file does not exist, then populate it with

-        patterns that match every file in the root directory and

-        no other directories, then will remove all directories tracked

-        by Git. Add patterns to the sparse-checkout file to

-        repopulate the working directory.

+        Enable the necessary config settings

+        (extensions.worktreeConfig, core.sparseCheckout,

+        core.sparseCheckoutCone) if they are not already enabled, and

+        write a set of patterns to the sparse-checkout file from the

+        list of arguments following the <em>set</em> subcommand. Update the

+        working directory to match the new patterns.

 </p>

-<div class="paragraph"><p>To avoid interfering with other worktrees, it first enables the

-<code>extensions.worktreeConfig</code> setting and makes sure to set the

-<code>core.sparseCheckout</code> setting in the worktree-specific config file.</p></div>

-<div class="paragraph"><p>When <code>--cone</code> is provided, the <code>core.sparseCheckoutCone</code> setting is

-also set, allowing for better performance with a limited set of

-patterns (see <em>CONE PATTERN SET</em> below).</p></div>

-<div class="paragraph"><p>Use the <code>--[no-]sparse-index</code> option to toggle the use of the sparse

-index format. This reduces the size of the index to be more closely

-aligned with your sparse-checkout definition. This can have significant

-performance advantages for commands such as <code>git status</code> or <code>git add</code>.

-This feature is still experimental. Some commands might be slower with

-a sparse index until they are properly integrated with the feature.</p></div>

+<div class="paragraph"><p>When the <code>--stdin</code> option is provided, the patterns are read from

+standard in as a newline-delimited list instead of from the arguments.</p></div>

+<div class="paragraph"><p>When <code>--cone</code> is passed or <code>core.sparseCheckoutCone</code> is enabled, the

+input list is considered a list of directories instead of

+sparse-checkout patterns.  This allows for better performance with a

+limited set of patterns (see <em>CONE PATTERN SET</em> below).  Note that the

+set command will write patterns to the sparse-checkout file to include

+all files contained in those directories (recursively) as well as

+files that are siblings of ancestor directories. The input format

+matches the output of <code>git ls-tree --name-only</code>.  This includes

+interpreting pathnames that begin with a double quote (") as C-style

+quoted strings.  This may become the default in the future; --no-cone

+can be passed to request non-cone mode.</p></div>

+<div class="paragraph"><p>Use the <code>--[no-]sparse-index</code> option to use a sparse index (the

+default is to not use it).  A sparse index reduces the size of the

+index to be more closely aligned with your sparse-checkout

+definition. This can have significant performance advantages for

+commands such as <code>git status</code> or <code>git add</code>.  This feature is still

+experimental. Some commands might be slower with a sparse index until

+they are properly integrated with the feature.</p></div>

 <div class="paragraph"><p><strong>WARNING:</strong> Using a sparse index requires modifying the index in a way

 that is not completely understood by external tools. If you have trouble

 with this compatibility, then run <code>git sparse-checkout init --no-sparse-index</code>

@@ -808,26 +816,6 @@ understand the sparse directory entries index extension and may fail to
 interact with your repository until it is disabled.</p></div>

 </dd>

 <dt class="hdlist1">

-<em>set</em>

-</dt>

-<dd>

-<p>

-        Write a set of patterns to the sparse-checkout file, as given as

-        a list of arguments following the <em>set</em> subcommand. Update the

-        working directory to match the new patterns. Enable the

-        core.sparseCheckout config setting if it is not already enabled.

-</p>

-<div class="paragraph"><p>When the <code>--stdin</code> option is provided, the patterns are read from

-standard in as a newline-delimited list instead of from the arguments.</p></div>

-<div class="paragraph"><p>When <code>core.sparseCheckoutCone</code> is enabled, the input list is considered a

-list of directories instead of sparse-checkout patterns. The command writes

-patterns to the sparse-checkout file to include all files contained in those

-directories (recursively) as well as files that are siblings of ancestor

-directories. The input format matches the output of <code>git ls-tree --name-only</code>.

-This includes interpreting pathnames that begin with a double quote (") as

-C-style quoted strings.</p></div>

-</dd>

-<dt class="hdlist1">

 <em>add</em>

 </dt>

 <dd>

@@ -853,6 +841,10 @@ C-style quoted strings.</p></div>
         after cleaning up affected paths (e.g. resolving conflicts, undoing

         or committing changes, etc.).

 </p>

+<div class="paragraph"><p>The <code>reapply</code> command can also take <code>--[no-]cone</code> and <code>--[no-]sparse-index</code>

+flags, with the same meaning as the flags from the <code>set</code> command, in order

+to change which sparsity mode you are using without needing to also respecify

+all sparsity paths.</p></div>

 </dd>

 <dt class="hdlist1">

 <em>disable</em>

@@ -860,10 +852,31 @@ C-style quoted strings.</p></div>
 <dd>

 <p>

         Disable the <code>core.sparseCheckout</code> config setting, and restore the

-        working directory to include all files. Leaves the sparse-checkout

-        file intact so a later <em>git sparse-checkout init</em> command may

-        return the working directory to the same state.

+        working directory to include all files.

+</p>

+</dd>

+<dt class="hdlist1">

+<em>init</em>

+</dt>

+<dd>

+<p>

+        Deprecated command that behaves like <code>set</code> with no specified paths.

+        May be removed in the future.

 </p>

+<div class="paragraph"><p>Historically, <code>set</code> did not handle all the necessary config settings,

+which meant that both <code>init</code> and <code>set</code> had to be called.  Invoking

+both meant the <code>init</code> step would first remove nearly all tracked files

+(and in cone mode, ignored files too), then the <code>set</code> step would add

+many of the tracked files (but not ignored files) back.  In addition

+to the lost files, the performance and UI of this combination was

+poor.</p></div>

+<div class="paragraph"><p>Also, historically, <code>init</code> would not actually initialize the

+sparse-checkout file if it already existed.  This meant it was

+possible to return to a sparse-checkout without remembering which

+paths to pass to a subsequent <em>set</em> or <em>add</em> command.  However,

+<code>--cone</code> and <code>--sparse-index</code> options would not be remembered across

+the disable command, so the easy restore of calling a plain <code>init</code>

+decreased in utility.</p></div>

 </dd>

 </dl></div>

 </div>

@@ -875,7 +888,7 @@ C-style quoted strings.</p></div>
 It uses the skip-worktree bit (see <a href="git-update-index.html">git-update-index(1)</a>) to tell

 Git whether a file in the working directory is worth looking at. If

 the skip-worktree bit is set, then the file is ignored in the working

-directory. Git will not populate the contents of those files, which

+directory. Git will avoid populating the contents of those files, which

 makes a sparse checkout helpful when working in a repository with many

 files, but only a few are important to the current user.</p></div>

 <div class="paragraph"><p>The <code>$GIT_DIR/info/sparse-checkout</code> file is used to define the

@@ -883,10 +896,8 @@ skip-worktree reference bitmap. When Git updates the working
 directory, it updates the skip-worktree bits in the index based

 on this file. The files matching the patterns in the file will

 appear in the working directory, and the rest will not.</p></div>

-<div class="paragraph"><p>To enable the sparse-checkout feature, run <code>git sparse-checkout init</code> to

-initialize a simple sparse-checkout file and enable the <code>core.sparseCheckout</code>

-config setting. Then, run <code>git sparse-checkout set</code> to modify the patterns in

-the sparse-checkout file.</p></div>

+<div class="paragraph"><p>To enable the sparse-checkout feature, run <code>git sparse-checkout set</code> to

+set the patterns you want to use.</p></div>

 <div class="paragraph"><p>To repopulate the working directory with all files, use the

 <code>git sparse-checkout disable</code> command.</p></div>

 </div>

@@ -1030,7 +1041,7 @@ of these restrictions.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2021-12-10 14:52:02 PST

+ 2022-01-03 16:49:08 PST

 </div>

 </div>

 </body>

diff --git a/git-sparse-checkout.txt b/git-sparse-checkout.txt
index 9a78dd721..b81dbe065 100644
--- a/git-sparse-checkout.txt
+++ b/git-sparse-checkout.txt
@@ -30,28 +30,36 @@ COMMANDS
 'list'::
 	Describe the patterns in the sparse-checkout file.
 
-'init'::
-	Enable the `core.sparseCheckout` setting. If the
-	sparse-checkout file does not exist, then populate it with
-	patterns that match every file in the root directory and
-	no other directories, then will remove all directories tracked
-	by Git. Add patterns to the sparse-checkout file to
-	repopulate the working directory.
+'set'::
+	Enable the necessary config settings
+	(extensions.worktreeConfig, core.sparseCheckout,
+	core.sparseCheckoutCone) if they are not already enabled, and
+	write a set of patterns to the sparse-checkout file from the
+	list of arguments following the 'set' subcommand. Update the
+	working directory to match the new patterns.
 +
-To avoid interfering with other worktrees, it first enables the
-`extensions.worktreeConfig` setting and makes sure to set the
-`core.sparseCheckout` setting in the worktree-specific config file.
+When the `--stdin` option is provided, the patterns are read from
+standard in as a newline-delimited list instead of from the arguments.
 +
-When `--cone` is provided, the `core.sparseCheckoutCone` setting is
-also set, allowing for better performance with a limited set of
-patterns (see 'CONE PATTERN SET' below).
+When `--cone` is passed or `core.sparseCheckoutCone` is enabled, the
+input list is considered a list of directories instead of
+sparse-checkout patterns.  This allows for better performance with a
+limited set of patterns (see 'CONE PATTERN SET' below).  Note that the
+set command will write patterns to the sparse-checkout file to include
+all files contained in those directories (recursively) as well as
+files that are siblings of ancestor directories. The input format
+matches the output of `git ls-tree --name-only`.  This includes
+interpreting pathnames that begin with a double quote (") as C-style
+quoted strings.  This may become the default in the future; --no-cone
+can be passed to request non-cone mode.
 +
-Use the `--[no-]sparse-index` option to toggle the use of the sparse
-index format. This reduces the size of the index to be more closely
-aligned with your sparse-checkout definition. This can have significant
-performance advantages for commands such as `git status` or `git add`.
-This feature is still experimental. Some commands might be slower with
-a sparse index until they are properly integrated with the feature.
+Use the `--[no-]sparse-index` option to use a sparse index (the
+default is to not use it).  A sparse index reduces the size of the
+index to be more closely aligned with your sparse-checkout
+definition. This can have significant performance advantages for
+commands such as `git status` or `git add`.  This feature is still
+experimental. Some commands might be slower with a sparse index until
+they are properly integrated with the feature.
 +
 **WARNING:** Using a sparse index requires modifying the index in a way
 that is not completely understood by external tools. If you have trouble
@@ -60,23 +68,6 @@ to rewrite your index to not be sparse. Older versions of Git will not
 understand the sparse directory entries index extension and may fail to
 interact with your repository until it is disabled.
 
-'set'::
-	Write a set of patterns to the sparse-checkout file, as given as
-	a list of arguments following the 'set' subcommand. Update the
-	working directory to match the new patterns. Enable the
-	core.sparseCheckout config setting if it is not already enabled.
-+
-When the `--stdin` option is provided, the patterns are read from
-standard in as a newline-delimited list instead of from the arguments.
-+
-When `core.sparseCheckoutCone` is enabled, the input list is considered a
-list of directories instead of sparse-checkout patterns. The command writes
-patterns to the sparse-checkout file to include all files contained in those
-directories (recursively) as well as files that are siblings of ancestor
-directories. The input format matches the output of `git ls-tree --name-only`.
-This includes interpreting pathnames that begin with a double quote (") as
-C-style quoted strings.
-
 'add'::
 	Update the sparse-checkout file to include additional patterns.
 	By default, these patterns are read from the command-line arguments,
@@ -93,12 +84,35 @@ C-style quoted strings.
 	cases, it can make sense to run `git sparse-checkout reapply` later
 	after cleaning up affected paths (e.g. resolving conflicts, undoing
 	or committing changes, etc.).
++
+The `reapply` command can also take `--[no-]cone` and `--[no-]sparse-index`
+flags, with the same meaning as the flags from the `set` command, in order
+to change which sparsity mode you are using without needing to also respecify
+all sparsity paths.
 
 'disable'::
 	Disable the `core.sparseCheckout` config setting, and restore the
-	working directory to include all files. Leaves the sparse-checkout
-	file intact so a later 'git sparse-checkout init' command may
-	return the working directory to the same state.
+	working directory to include all files.
+
+'init'::
+	Deprecated command that behaves like `set` with no specified paths.
+	May be removed in the future.
++
+Historically, `set` did not handle all the necessary config settings,
+which meant that both `init` and `set` had to be called.  Invoking
+both meant the `init` step would first remove nearly all tracked files
+(and in cone mode, ignored files too), then the `set` step would add
+many of the tracked files (but not ignored files) back.  In addition
+to the lost files, the performance and UI of this combination was
+poor.
++
+Also, historically, `init` would not actually initialize the
+sparse-checkout file if it already existed.  This meant it was
+possible to return to a sparse-checkout without remembering which
+paths to pass to a subsequent 'set' or 'add' command.  However,
+`--cone` and `--sparse-index` options would not be remembered across
+the disable command, so the easy restore of calling a plain `init`
+decreased in utility.
 
 SPARSE CHECKOUT
 ---------------
@@ -107,7 +121,7 @@ SPARSE CHECKOUT
 It uses the skip-worktree bit (see linkgit:git-update-index[1]) to tell
 Git whether a file in the working directory is worth looking at. If
 the skip-worktree bit is set, then the file is ignored in the working
-directory. Git will not populate the contents of those files, which
+directory. Git will avoid populating the contents of those files, which
 makes a sparse checkout helpful when working in a repository with many
 files, but only a few are important to the current user.
 
@@ -117,10 +131,8 @@ directory, it updates the skip-worktree bits in the index based
 on this file. The files matching the patterns in the file will
 appear in the working directory, and the rest will not.
 
-To enable the sparse-checkout feature, run `git sparse-checkout init` to
-initialize a simple sparse-checkout file and enable the `core.sparseCheckout`
-config setting. Then, run `git sparse-checkout set` to modify the patterns in
-the sparse-checkout file.
+To enable the sparse-checkout feature, run `git sparse-checkout set` to
+set the patterns you want to use.
 
 To repopulate the working directory with all files, use the
 `git sparse-checkout disable` command.
diff --git a/howto/coordinate-embargoed-releases.html b/howto/coordinate-embargoed-releases.html
index 1d375d6a7..3418b430c 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

- 2021-12-23 00:29:55 PST

+ 2022-01-03 16:49:32 PST

 </div>

 </div>

 </body>

diff --git a/howto/keep-canonical-history-correct.html b/howto/keep-canonical-history-correct.html
index ebce36fb8..40434f022 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

- 2021-12-23 00:29:54 PST

+ 2022-01-03 16:49:32 PST

 </div>

 </div>

 </body>

diff --git a/howto/maintain-git.html b/howto/maintain-git.html
index be3bf4a12..46d8049a9 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

- 2021-12-23 00:29:55 PST

+ 2022-01-03 16:49:32 PST

 </div>

 </div>

 </body>

diff --git a/howto/new-command.html b/howto/new-command.html
index ca850876d..4d9ba0791 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

- 2021-12-23 00:29:53 PST

+ 2022-01-03 16:49:30 PST

 </div>

 </div>

 </body>

diff --git a/howto/rebase-from-internal-branch.html b/howto/rebase-from-internal-branch.html
index 414f52db3..10af21cda 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

- 2021-12-23 00:29:54 PST

+ 2022-01-03 16:49:32 PST

 </div>

 </div>

 </body>

diff --git a/howto/rebuild-from-update-hook.html b/howto/rebuild-from-update-hook.html
index 06114d55b..52582321d 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

- 2021-12-23 00:29:54 PST

+ 2022-01-03 16:49:32 PST

 </div>

 </div>

 </body>

diff --git a/howto/recover-corrupted-blob-object.html b/howto/recover-corrupted-blob-object.html
index 6b122840b..f4ebcfbd7 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

- 2021-12-23 00:29:54 PST

+ 2022-01-03 16:49:31 PST

 </div>

 </div>

 </body>

diff --git a/howto/recover-corrupted-object-harder.html b/howto/recover-corrupted-object-harder.html
index 7cd66a3f7..2911528c9 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

- 2021-12-23 00:29:54 PST

+ 2022-01-03 16:49:31 PST

 </div>

 </div>

 </body>

diff --git a/howto/revert-a-faulty-merge.html b/howto/revert-a-faulty-merge.html
index 64ad7137c..1f8861c71 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

- 2021-12-23 00:29:54 PST

+ 2022-01-03 16:49:31 PST

 </div>

 </div>

 </body>

diff --git a/howto/revert-branch-rebase.html b/howto/revert-branch-rebase.html
index 265683242..45ca9392b 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

- 2021-12-23 00:29:53 PST

+ 2022-01-03 16:49:30 PST

 </div>

 </div>

 </body>

diff --git a/howto/separating-topic-branches.html b/howto/separating-topic-branches.html
index 5143a8b5b..b7792ab01 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

- 2021-12-23 00:29:54 PST

+ 2022-01-03 16:49:31 PST

 </div>

 </div>

 </body>

diff --git a/howto/setup-git-server-over-http.html b/howto/setup-git-server-over-http.html
index 1ea42eb61..780edd8fc 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

- 2021-12-23 00:29:54 PST

+ 2022-01-03 16:49:31 PST

 </div>

 </div>

 </body>

diff --git a/howto/update-hook-example.html b/howto/update-hook-example.html
index 34d226c5b..e55b19a79 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

- 2021-12-23 00:29:54 PST

+ 2022-01-03 16:49:31 PST

 </div>

 </div>

 </body>

diff --git a/howto/use-git-daemon.html b/howto/use-git-daemon.html
index 1f9095515..98fa8315b 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

- 2021-12-23 00:29:53 PST

+ 2022-01-03 16:49:31 PST

 </div>

 </div>

 </body>

diff --git a/howto/using-merge-subtree.html b/howto/using-merge-subtree.html
index 1c8a700dc..8c6fd8514 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

- 2021-12-23 00:29:53 PST

+ 2022-01-03 16:49:30 PST

 </div>

 </div>

 </body>

diff --git a/howto/using-signed-tag-in-pull-request.html b/howto/using-signed-tag-in-pull-request.html
index 96d89b29d..4f7b3e662 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

- 2021-12-23 00:29:53 PST

+ 2022-01-03 16:49:30 PST

 </div>

 </div>

 </body>