Autogenerated HTML docs for v2.33.0-785-g2a972

20 files changed, 47 insertions, 35 deletions

diff --git a/RelNotes/2.34.0.txt b/RelNotes/2.34.0.txt
index 9d583ead0..6c9c5301f 100644
--- a/RelNotes/2.34.0.txt
+++ b/RelNotes/2.34.0.txt
@@ -141,6 +141,11 @@ Performance, Internal Implementation, Development Support etc.
 
  * Remove external declaration of functions that no longer exist.
 
+ * "git multi-pack-index write --bitmap" learns to propagate the
+   hashcache from original bitmap to resulting bitmap.
+
+ * CI learns to run the leak sanitizer builds.
+
 
 Fixes since v2.33
 -----------------
@@ -351,3 +356,5 @@ Fixes since v2.33
    (merge 51b04c05b7 bs/difftool-msg-tweak later to maint).
    (merge dd20e4a6db ab/make-compdb-fix later to maint).
    (merge 6ffb990dc4 os/status-docfix later to maint).
+   (merge 100c2da2d3 rs/p3400-lose-tac later to maint).
+   (merge 76f3b69896 tb/aggregate-ignore-leading-whitespaces later to maint).
diff --git a/git-config.html b/git-config.html
index a91315653..ea8507689 100644
--- a/git-config.html
+++ b/git-config.html
@@ -8193,6 +8193,9 @@ pack.writeBitmapHashCache
         pushed since the last gc). The downside is that it consumes 4

         bytes per object of disk space. Defaults to true.

 </p>

+<div class="paragraph"><p>When writing a multi-pack reachability bitmap, no new namehashes are

+computed; instead, any namehashes stored in an existing bitmap are

+permuted into their appropriate location when writing a new bitmap.</p></div>

 </dd>

 <dt class="hdlist1">

 pack.writeReverseIndex

diff --git a/git.html b/git.html
index 034634924..b33ec7039 100644
--- a/git.html
+++ b/git.html
@@ -3419,15 +3419,16 @@ for full details.</p></div>
 </dt>

 <dd>

 <p>

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

-        over lists of refs. In a normal, non-corrupted repository, this

-        does nothing. However, enabling it may help git to detect and

-        abort some operations in the presence of broken refs. Git sets

-        this variable automatically when performing destructive

-        operations like <a href="git-prune.html">git-prune(1)</a>. You should not need to set

-        it yourself unless you want to be paranoid about making sure

-        an operation has touched every ref (e.g., because you are

-        cloning a repository to make a backup).

+        If set to <code>0</code>, 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.,

+        <a href="git-prune.html">git-prune(1)</a>) are better off aborting rather than

+        ignoring broken refs (and thus considering the history they

+        point to as not worth saving). The default value is <code>1</code> (i.e.,

+        be paranoid about detecting and aborting all operations). You

+        should not normally need to set this to <code>0</code>, but it may be

+        useful when trying to salvage data from a corrupted repository.

 </p>

 </dd>

 <dt class="hdlist1">

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

 <div id="footer-text">

 Last updated

- 2021-09-23 14:33:59 PDT

+ 2021-10-11 12:48:01 PDT

 </div>

 </div>

 </body>

diff --git a/git.txt b/git.txt
index abace9eac..d63c65e67 100644
--- a/git.txt
+++ b/git.txt
@@ -867,15 +867,16 @@ for full details.
 	end user, to be recorded in the body of the reflog.
 
 `GIT_REF_PARANOIA`::
-	If set to `1`, include broken or badly named refs when iterating
-	over lists of refs. In a normal, non-corrupted repository, this
-	does nothing. However, enabling it may help git to detect and
-	abort some operations in the presence of broken refs. Git sets
-	this variable automatically when performing destructive
-	operations like linkgit:git-prune[1]. You should not need to set
-	it yourself unless you want to be paranoid about making sure
-	an operation has touched every ref (e.g., because you are
-	cloning a repository to make a backup).
+	If set to `0`, 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.,
+	linkgit:git-prune[1]) are better off aborting rather than
+	ignoring broken refs (and thus considering the history they
+	point to as not worth saving). The default value is `1` (i.e.,
+	be paranoid about detecting and aborting all operations). You
+	should not normally need to set this to `0`, but it may be
+	useful when trying to salvage data from a corrupted repository.
 
 `GIT_ALLOW_PROTOCOL`::
 	If set to a colon-separated list of protocols, behave as if
diff --git a/howto/coordinate-embargoed-releases.html b/howto/coordinate-embargoed-releases.html
index 64922c461..b0510b64a 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-10-06 14:17:15 PDT

+ 2021-10-11 12:48:37 PDT

 </div>

 </div>

 </body>

diff --git a/howto/keep-canonical-history-correct.html b/howto/keep-canonical-history-correct.html
index 6d1dab7ae..41a376d64 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-10-06 14:17:14 PDT

+ 2021-10-11 12:48:37 PDT

 </div>

 </div>

 </body>

diff --git a/howto/maintain-git.html b/howto/maintain-git.html
index 230d39d32..0d76a837b 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-10-06 14:17:15 PDT

+ 2021-10-11 12:48:37 PDT

 </div>

 </div>

 </body>

diff --git a/howto/new-command.html b/howto/new-command.html
index a5ae462f4..71c9c5281 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-10-06 14:17:12 PDT

+ 2021-10-11 12:48:35 PDT

 </div>

 </div>

 </body>

diff --git a/howto/rebase-from-internal-branch.html b/howto/rebase-from-internal-branch.html
index 163fe0354..f9e3ae2d6 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-10-06 14:17:14 PDT

+ 2021-10-11 12:48:37 PDT

 </div>

 </div>

 </body>

diff --git a/howto/rebuild-from-update-hook.html b/howto/rebuild-from-update-hook.html
index 1b22416bc..82515d7a3 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-10-06 14:17:14 PDT

+ 2021-10-11 12:48:37 PDT

 </div>

 </div>

 </body>

diff --git a/howto/recover-corrupted-blob-object.html b/howto/recover-corrupted-blob-object.html
index 9e53b3626..7aeb62ff9 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-10-06 14:17:14 PDT

+ 2021-10-11 12:48:37 PDT

 </div>

 </div>

 </body>

diff --git a/howto/recover-corrupted-object-harder.html b/howto/recover-corrupted-object-harder.html
index e53fcde49..acb2f43ec 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-10-06 14:17:14 PDT

+ 2021-10-11 12:48:37 PDT

 </div>

 </div>

 </body>

diff --git a/howto/revert-a-faulty-merge.html b/howto/revert-a-faulty-merge.html
index 60f2c7275..e7c29e868 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-10-06 14:17:14 PDT

+ 2021-10-11 12:48:36 PDT

 </div>

 </div>

 </body>

diff --git a/howto/revert-branch-rebase.html b/howto/revert-branch-rebase.html
index 563b2146f..72cd53430 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-10-06 14:17:12 PDT

+ 2021-10-11 12:48:35 PDT

 </div>

 </div>

 </body>

diff --git a/howto/separating-topic-branches.html b/howto/separating-topic-branches.html
index db386ef8c..14d1e3049 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-10-06 14:17:13 PDT

+ 2021-10-11 12:48:36 PDT

 </div>

 </div>

 </body>

diff --git a/howto/setup-git-server-over-http.html b/howto/setup-git-server-over-http.html
index 2e4c51738..df01a313b 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-10-06 14:17:13 PDT

+ 2021-10-11 12:48:36 PDT

 </div>

 </div>

 </body>

diff --git a/howto/update-hook-example.html b/howto/update-hook-example.html
index e65eff875..bc21bc680 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-10-06 14:17:13 PDT

+ 2021-10-11 12:48:36 PDT

 </div>

 </div>

 </body>

diff --git a/howto/use-git-daemon.html b/howto/use-git-daemon.html
index 3e771a621..bbd5909f3 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-10-06 14:17:13 PDT

+ 2021-10-11 12:48:36 PDT

 </div>

 </div>

 </body>

diff --git a/howto/using-merge-subtree.html b/howto/using-merge-subtree.html
index bc2df5df3..077f5ebcb 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-10-06 14:17:12 PDT

+ 2021-10-11 12:48:35 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 b16403227..951628d3c 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-10-06 14:17:13 PDT

+ 2021-10-11 12:48:35 PDT

 </div>

 </div>

 </body>