Autogenerated HTML docs for v2.46.0-rc1

git · Jul 18, 2024 · 84f1873 · 84f1873
1 parent d6b0be5
commit 84f1873
Show file tree

Hide file tree

Showing 54 changed files with 98 additions and 90 deletions.
diff --git a/DecisionMaking.html b/DecisionMaking.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>Decision-Making Process in the Git Project</h1>
-<span id="revdate">2024-07-17</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div class="sect1">

diff --git a/MyFirstContribution.html b/MyFirstContribution.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>My First Contribution to the Git Project</h1>
-<span id="revdate">2024-07-17</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div class="sect1">

diff --git a/MyFirstObjectWalk.html b/MyFirstObjectWalk.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>My First Object Walk</h1>
-<span id="revdate">2024-07-17</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div class="sect1">

diff --git a/RelNotes/2.46.0.txt b/RelNotes/2.46.0.txt
@@ -451,3 +451,4 @@ Fixes since v2.45
    (merge 00f3661a0a ss/doc-eol-attr-fix later to maint).
    (merge 428c40da61 ri/doc-show-branch-fix later to maint).
    (merge 58696bfcaa jc/where-is-bash-for-ci later to maint).
+   (merge 616e94ca24 tb/doc-max-tree-depth-fix later to maint).
diff --git a/ReviewingGuidelines.html b/ReviewingGuidelines.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>Reviewing Patches in the Git Project</h1>
-<span id="revdate">2024-07-17</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div class="sect1">

diff --git a/SubmittingPatches.html b/SubmittingPatches.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>Submitting Patches</h1>
-<span id="revdate">2024-07-17</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div class="sect1">
@@ -1708,7 +1708,7 @@ <h3 id="_gnus">Gnus</h3>
 <div id="footer">
 <div id="footer-text">
 Last updated
- 2024-07-12 09:18:17 PDT
+ 2024-07-18 09:52:51 PDT
 </div>
 </div>
 </body>

diff --git a/ToolsForGit.html b/ToolsForGit.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>Tools for developing Git</h1>
-<span id="revdate">2024-07-17</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div class="sect1">

diff --git a/everyday.html b/everyday.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>Everyday Git With 20 Commands Or So</h1>
-<span id="revdate">2024-07-17</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div id="preamble">

diff --git a/git-bisect-lk2009.html b/git-bisect-lk2009.html
@@ -737,7 +737,7 @@
 <h1>Fighting regressions with git bisect</h1>
 <span id="author">Christian Couder</span><br />
 <span id="email"><code>&lt;<a href="mailto:[email protected]">[email protected]</a>&gt;</code></span><br />
-<span id="revdate">2024-07-12</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div class="sect1">

diff --git a/git-config.html b/git-config.html
@@ -4969,7 +4969,8 @@ <h3 id="_variables">Variables</h3>
         The maximum depth Git is willing to recurse while traversing a
         tree (e.g., "a/b/cde/f" has a depth of 4). This is a fail-safe
         to allow Git to abort cleanly, and should not generally need to
-        be adjusted. The default is 4096.
+        be adjusted. When Git is compiled with MSVC, the default is 512.
+        Otherwise, the default is 2048.
 </p>
 </dd>
 <dt class="hdlist1">

diff --git a/git-remote-helpers.html b/git-remote-helpers.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>git-remote-helpers</h1>
-<span id="revdate">2024-07-17</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div id="preamble">

diff --git a/git-tools.html b/git-tools.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>Git Tools</h1>
-<span id="revdate">2024-07-12</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div id="preamble">

diff --git a/gitglossary.html b/gitglossary.html
@@ -1684,7 +1684,7 @@ <h2 id="_description">DESCRIPTION</h2>
 </dt>
 <dd>
 <p>
-        A name that that points to an <a href="#def_object_name">object name</a> or
+        A name that points to an <a href="#def_object_name">object name</a> or
         another ref (the latter is called a <a href="#def_symref">symbolic ref</a>).
         For convenience, a ref can sometimes be abbreviated when used
         as an argument to a Git command; see <a href="gitrevisions.html">gitrevisions(7)</a>

diff --git a/gitpacking.html b/gitpacking.html
@@ -1015,39 +1015,39 @@ <h3 id="_examples">Examples</h3>
 <div class="paragraph"><p>Suppose that you have a repository with a large number of references,
 and you want a bare-bones configuration of pseudo-merge bitmaps that
 will enhance bitmap coverage of the <code>refs/</code> namespace. You may start
-wiht a configuration like so:</p></div>
-<div class="literalblock">
+with a configuration like so:</p></div>
+<div class="listingblock">
 <div class="content">
 <pre><code>[bitmapPseudoMerge "all"]
-    pattern = "refs/"
-    threshold = now
-    stableThreshold = never
-    sampleRate = 100
-    maxMerges = 64</code></pre>
+        pattern = "refs/"
+        threshold = now
+        stableThreshold = never
+        sampleRate = 100
+        maxMerges = 64</code></pre>
 </div></div>
 <div class="paragraph"><p>This will create pseudo-merge bitmaps for all references, regardless of
 their age, and group them into 64 pseudo-merge commits.</p></div>
 <div class="paragraph"><p>If you wanted to separate tags from branches when generating
 pseudo-merge commits, you would instead define the pattern with a
 capture group, like so:</p></div>
-<div class="literalblock">
+<div class="listingblock">
 <div class="content">
 <pre><code>[bitmapPseudoMerge "all"]
-    pattern = "refs/(heads/tags)/"</code></pre>
+        pattern = "refs/(heads/tags)/"</code></pre>
 </div></div>
 <div class="paragraph"><p>Suppose instead that you are working in a fork-network repository, with
 each fork specified by some numeric ID, and whose refs reside in
 <code>refs/virtual/NNN/</code> (where <code>NNN</code> is the numeric ID corresponding to some
 fork) in the network. In this instance, you may instead write something
 like:</p></div>
-<div class="literalblock">
+<div class="listingblock">
 <div class="content">
 <pre><code>[bitmapPseudoMerge "all"]
-    pattern = "refs/virtual/([0-9]+)/(heads|tags)/"
-    threshold = now
-    stableThreshold = never
-    sampleRate = 100
-    maxMerges = 64</code></pre>
+        pattern = "refs/virtual/([0-9]+)/(heads|tags)/"
+        threshold = now
+        stableThreshold = never
+        sampleRate = 100
+        maxMerges = 64</code></pre>
 </div></div>
 <div class="paragraph"><p>Which would generate pseudo-merge group identifiers like "1234-heads",
 and "5678-tags" (for branches in fork "1234", and tags in remote "5678",
@@ -1073,7 +1073,7 @@ <h2 id="_git">GIT</h2>
 <div id="footer">
 <div id="footer-text">
 Last updated
- 2024-06-24 17:32:59 PDT
+ 2024-07-18 09:52:44 PDT
 </div>
 </div>
 </body>

diff --git a/gitpacking.txt b/gitpacking.txt
@@ -143,14 +143,16 @@ include::config/bitmap-pseudo-merge.txt[]
 Suppose that you have a repository with a large number of references,
 and you want a bare-bones configuration of pseudo-merge bitmaps that
 will enhance bitmap coverage of the `refs/` namespace. You may start
-wiht a configuration like so:
+with a configuration like so:
 
-    [bitmapPseudoMerge "all"]
+----
+[bitmapPseudoMerge "all"]
 	pattern = "refs/"
 	threshold = now
 	stableThreshold = never
 	sampleRate = 100
 	maxMerges = 64
+----
 
 This will create pseudo-merge bitmaps for all references, regardless of
 their age, and group them into 64 pseudo-merge commits.
@@ -159,21 +161,25 @@ If you wanted to separate tags from branches when generating
 pseudo-merge commits, you would instead define the pattern with a
 capture group, like so:
 
-    [bitmapPseudoMerge "all"]
+----
+[bitmapPseudoMerge "all"]
 	pattern = "refs/(heads/tags)/"
+----
 
 Suppose instead that you are working in a fork-network repository, with
 each fork specified by some numeric ID, and whose refs reside in
 `refs/virtual/NNN/` (where `NNN` is the numeric ID corresponding to some
 fork) in the network. In this instance, you may instead write something
 like:
 
-    [bitmapPseudoMerge "all"]
+----
+[bitmapPseudoMerge "all"]
 	pattern = "refs/virtual/([0-9]+)/(heads|tags)/"
 	threshold = now
 	stableThreshold = never
 	sampleRate = 100
 	maxMerges = 64
+----
 
 Which would generate pseudo-merge group identifiers like "1234-heads",
 and "5678-tags" (for branches in fork "1234", and tags in remote "5678",

diff --git a/glossary-content.txt b/glossary-content.txt
@@ -550,7 +550,7 @@ The following pseudorefs are known to Git:
 	to the result.
 
 [[def_ref]]ref::
-	A name that that points to an <<def_object_name,object name>> or
+	A name that points to an <<def_object_name,object name>> or
 	another ref (the latter is called a <<def_symref,symbolic ref>>).
 	For convenience, a ref can sometimes be abbreviated when used
 	as an argument to a Git command; see linkgit:gitrevisions[7]

diff --git a/howto-index.html b/howto-index.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>Git Howto Index</h1>
-<span id="revdate">2024-07-12</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div id="preamble">
@@ -896,7 +896,7 @@ <h1>Git Howto Index</h1>
 <div id="footer">
 <div id="footer-text">
 Last updated
- 2024-07-12 09:18:14 PDT
+ 2024-07-18 09:52:49 PDT
 </div>
 </div>
 </body>

diff --git a/howto/coordinate-embargoed-releases.html b/howto/coordinate-embargoed-releases.html
@@ -1038,7 +1038,7 @@ <h3 id="_example_mail_to_a_href_mailto_oss_security_lists_openwall_com_oss_secur
 <div id="footer">
 <div id="footer-text">
 Last updated
- 2024-07-17 13:35:44 PDT
+ 2024-07-18 09:52:51 PDT
 </div>
 </div>
 </body>

diff --git a/howto/keep-canonical-history-correct.html b/howto/keep-canonical-history-correct.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>Keep authoritative canonical history correct with git pull</h1>
-<span id="revdate">2024-07-17</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div id="preamble">
@@ -939,7 +939,7 @@ <h1>Keep authoritative canonical history correct with git pull</h1>
 <div id="footer">
 <div id="footer-text">
 Last updated
- 2024-07-17 13:35:44 PDT
+ 2024-07-18 09:52:50 PDT
 </div>
 </div>
 </body>

diff --git a/howto/maintain-git.html b/howto/maintain-git.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>How to maintain Git</h1>
-<span id="revdate">2024-07-17</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div class="sect1">
@@ -1479,7 +1479,7 @@ <h3 id="_preparing_a_merge_fix">Preparing a "merge-fix"</h3>
 <div id="footer">
 <div id="footer-text">
 Last updated
- 2024-07-17 13:35:44 PDT
+ 2024-07-18 09:52:51 PDT
 </div>
 </div>
 </body>

diff --git a/howto/new-command.html b/howto/new-command.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>How to integrate new subcommands</h1>
-<span id="revdate">2024-07-17</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div id="preamble">
@@ -864,7 +864,7 @@ <h2 id="_integrating_a_command">Integrating a command</h2>
 <div id="footer">
 <div id="footer-text">
 Last updated
- 2024-07-17 13:35:43 PDT
+ 2024-07-18 09:52:49 PDT
 </div>
 </div>
 </body>

diff --git a/howto/rebase-from-internal-branch.html b/howto/rebase-from-internal-branch.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>How to rebase from an internal branch</h1>
-<span id="revdate">2024-07-17</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div id="preamble">
@@ -896,7 +896,7 @@ <h1>How to rebase from an internal branch</h1>
 <div id="footer">
 <div id="footer-text">
 Last updated
- 2024-07-17 13:35:44 PDT
+ 2024-07-18 09:52:50 PDT
 </div>
 </div>
 </body>

diff --git a/howto/rebuild-from-update-hook.html b/howto/rebuild-from-update-hook.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>How to rebuild from update hook</h1>
-<span id="revdate">2024-07-17</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div id="preamble">
@@ -848,7 +848,7 @@ <h1>How to rebuild from update hook</h1>
 <div id="footer">
 <div id="footer-text">
 Last updated
- 2024-07-17 13:35:44 PDT
+ 2024-07-18 09:52:50 PDT
 </div>
 </div>
 </body>

diff --git a/howto/recover-corrupted-blob-object.html b/howto/recover-corrupted-blob-object.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>How to recover a corrupted blob object</h1>
-<span id="revdate">2024-07-17</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div id="preamble">
@@ -881,7 +881,7 @@ <h1>How to recover a corrupted blob object</h1>
 <div id="footer">
 <div id="footer-text">
 Last updated
- 2024-07-17 13:35:44 PDT
+ 2024-07-18 09:52:50 PDT
 </div>
 </div>
 </body>

diff --git a/howto/recover-corrupted-object-harder.html b/howto/recover-corrupted-object-harder.html
@@ -735,7 +735,7 @@
 <body class="article">
 <div id="header">
 <h1>How to recover an object from scratch</h1>
-<span id="revdate">2024-07-17</span>
+<span id="revdate">2024-07-18</span>
 </div>
 <div id="content">
 <div id="preamble">
@@ -1190,7 +1190,7 @@ <h2 id="_the_adventure_continues_8230">The adventure continues&#8230;</h2>
 <div id="footer">
 <div id="footer-text">
 Last updated
- 2024-07-17 13:35:44 PDT
+ 2024-07-18 09:52:50 PDT
 </div>
 </div>
 </body>