Autogenerated HTML docs for v2.47.0-rc1-33-g90fe38

Author: gitster

BreakingChanges.txt

@@ -117,7 +117,7 @@ Cf. <[email protected]>.
 
 * The git-pack-redundant(1) command can be used to remove redundant pack files.
   The subcommand is unusably slow and the reason why nobody reports it as a
-  performance bug is suspected to be the absense of users. We have nominated
+  performance bug is suspected to be the absence of users. We have nominated
   the command for removal and have started to emit a user-visible warning in
   c3b58472be (pack-redundant: gauge the usage before proposing its removal,
   2020-08-25) whenever the command is executed.

DecisionMaking.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Decision-Making Process in the Git Project</h1>
 <div class="details">
-<span id="revdate">2024-10-02</span>
+<span id="revdate">2024-10-04</span>
 </div>
 </div>
 <div id="content">
@@ -512,7 +512,7 @@ <h2 id="_larger_discussions_without_patches">Larger Discussions (without patches
 <div class="paragraph">
 <p>For non-technical decisions such as community norms or processes, it is up to
 the community as a whole to implement and sustain agreed-upon changes.
-The project leadership committe (PLC) may help the implementation of
+The project leadership committee (PLC) may help the implementation of
 policy decisions.</p>
 </div>
 </div>
@@ -540,7 +540,7 @@ <h2 id="_other_discussion_venues">Other Discussion Venues</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-05-30 16:24:27 -0700
+Last updated 2024-10-04 15:34:09 -0700
 </div>
 </div>
 </body>

DecisionMaking.txt

@@ -54,7 +54,7 @@ implementation, for very large changes).
 
 For non-technical decisions such as community norms or processes, it is up to
 the community as a whole to implement and sustain agreed-upon changes.
-The project leadership committe (PLC) may help the implementation of
+The project leadership committee (PLC) may help the implementation of
 policy decisions.
 
 

MyFirstContribution.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>My First Contribution to the Git Project</h1>
 <div class="details">
-<span id="revdate">2024-10-02</span>
+<span id="revdate">2024-10-04</span>
 </div>
 </div>
 <div id="content">

MyFirstObjectWalk.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>My First Object Walk</h1>
 <div class="details">
-<span id="revdate">2024-10-02</span>
+<span id="revdate">2024-10-04</span>
 </div>
 </div>
 <div id="content">

RelNotes/2.47.0.txt

@@ -328,10 +328,15 @@ Fixes since v2.46
    index" advice message, which has been corrected.
    (merge 537e516a39 ds/sparse-checkout-expansion-advice later to maint).
 
+ * macOS with fsmonitor daemon can hang forever when a submodule is
+   involved, which has been corrected.
+
  * Other code cleanup, docfix, build fix, etc.
    (merge be10ac7037 jc/mailinfo-header-cleanup later to maint).
    (merge 4460e052e0 jc/range-diff-lazy-setup later to maint).
    (merge 0627c58e7a ak/typofixes later to maint).
    (merge 83799f1500 jk/t9001-deflake later to maint).
    (merge e02cc08a88 ak/typofix-2.46-maint later to maint).
    (merge 5c5d29e1c4 ps/ci-gitlab-upgrade later to maint).
+   (merge 9c4c840901 jc/doc-discarding-stalled-topics later to maint).
+   (merge 5e6f359f6b ds/read-cache-mempool-leakfix later to maint).

ReviewingGuidelines.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Reviewing Patches in the Git Project</h1>
 <div class="details">
-<span id="revdate">2024-10-02</span>
+<span id="revdate">2024-10-04</span>
 </div>
 </div>
 <div id="content">

SubmittingPatches.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Submitting Patches</h1>
 <div class="details">
-<span id="revdate">2024-10-02</span>
+<span id="revdate">2024-10-04</span>
 </div>
 </div>
 <div id="content">

ToolsForGit.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Tools for developing Git</h1>
 <div class="details">
-<span id="revdate">2024-10-02</span>
+<span id="revdate">2024-10-04</span>
 </div>
 </div>
 <div id="content">

everyday.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Everyday Git With 20 Commands Or So</h1>
 <div class="details">
-<span id="revdate">2024-10-02</span>
+<span id="revdate">2024-10-04</span>
 </div>
 </div>
 <div id="content">

git-config.html

@@ -4412,7 +4412,7 @@ <h3 id="_variables">Variables</h3>
 </dd>
 <dt class="hdlist1">extensions.compatObjectFormat</dt>
 <dd>
-<p>Specify a compatitbility hash algorithm to use.  The acceptable values
+<p>Specify a compatibility hash algorithm to use.  The acceptable values
 are <code>sha1</code> and <code>sha256</code>.  The value specified must be different from the
 value of extensions.objectFormat.  This allows client level
 interoperability between git repositories whose objectFormat matches
@@ -5183,7 +5183,7 @@ <h3 id="_variables">Variables</h3>
 containing the filtered out objects. <strong>WARNING:</strong> The
 specified location should be accessible, using for example the
 Git alternates mechanism, otherwise the repo could be
-considered corrupt by Git as it migh not be able to access the
+considered corrupt by Git as it might not be able to access the
 objects in that packfile. See the <code>--filter-to=&lt;dir&gt;</code> option
 of <a href="git-repack.html">git-repack(1)</a> and the <code>objects/info/alternates</code>
 section of <a href="gitrepository-layout.html">gitrepository-layout(5)</a>.</p>
@@ -7983,7 +7983,7 @@ <h3 id="_variables">Variables</h3>
 <p>If true, this remote will be skipped when updating
 using <a href="git-fetch.html">git-fetch(1)</a>, the <code>update</code> subcommand of
 <a href="git-remote.html">git-remote(1)</a>, and ignored by the prefetch task
-of <code>git maitenance</code>.</p>
+of <code>git maintenance</code>.</p>
 </dd>
 <dt class="hdlist1">remote.&lt;name&gt;.receivepack</dt>
 <dd>

git-gc.html

@@ -794,7 +794,7 @@ <h2 id="_configuration">CONFIGURATION</h2>
 containing the filtered out objects. <strong>WARNING:</strong> The
 specified location should be accessible, using for example the
 Git alternates mechanism, otherwise the repo could be
-considered corrupt by Git as it migh not be able to access the
+considered corrupt by Git as it might not be able to access the
 objects in that packfile. See the <code>--filter-to=&lt;dir&gt;</code> option
 of <a href="git-repack.html">git-repack(1)</a> and the <code>objects/info/alternates</code>
 section of <a href="gitrepository-layout.html">gitrepository-layout(5)</a>.</p>

git-remote-helpers.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>git-remote-helpers</h1>
 <div class="details">
-<span id="revdate">2024-10-02</span>
+<span id="revdate">2024-10-04</span>
 </div>
 </div>
 <div id="content">

gitformat-commit-graph.html

@@ -647,7 +647,7 @@ <h4 id="_generation_data_overflow_id_g_d_o_2_optional">Generation Data Overflow
 </li>
 <li>
 <p>Generation Data Overflow chunk is present only when Generation Data
-chunk is present and atleast one corrected commit date offset cannot
+chunk is present and at least one corrected commit date offset cannot
 be stored within 31 bits.</p>
 </li>
 </ul>
@@ -773,7 +773,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-07-08 15:33:45 -0700
+Last updated 2024-10-04 15:34:09 -0700
 </div>
 </div>
 </body>

gitformat-commit-graph.txt

@@ -122,7 +122,7 @@ All multi-byte numbers are in network byte order.
       for commits with corrected commit date offsets that cannot be
       stored within 31 bits.
     * Generation Data Overflow chunk is present only when Generation Data
-      chunk is present and atleast one corrected commit date offset cannot
+      chunk is present and at least one corrected commit date offset cannot
       be stored within 31 bits.
 
 ==== Extra Edge List (ID: {'E', 'D', 'G', 'E'}) [Optional]

gitweb.html

@@ -760,7 +760,7 @@ <h3 id="_per_repository_gitweb_configuration">Per-repository gitweb configuratio
 </dd>
 <dt class="hdlist1">category (or <code>gitweb.category</code>)</dt>
 <dd>
-<p>Singe line category of a project, used to group projects if
+<p>Single line category of a project, used to group projects if
 <code>$projects_list_group_categories</code> is enabled.  By default (file and
 configuration variable absent), uncategorized projects are put in the
 <code>$project_list_default_category</code> category.  You can use the
@@ -1378,7 +1378,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-02-08 15:45:59 -0800
+Last updated 2024-10-04 15:34:09 -0700
 </div>
 </div>
 </body>

gitweb.txt

@@ -234,7 +234,7 @@ from the template during repository creation, usually installed in
 configuration variable, but the file takes precedence.
 
 category (or `gitweb.category`)::
-	Singe line category of a project, used to group projects if
+	Single line category of a project, used to group projects if
 	`$projects_list_group_categories` is enabled.  By default (file and
 	configuration variable absent), uncategorized projects are put in the
 	`$project_list_default_category` category.  You can use the

howto-index.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Git Howto Index</h1>
 <div class="details">
-<span id="revdate">2024-10-02</span>
+<span id="revdate">2024-10-04</span>
 </div>
 </div>
 <div id="content">
@@ -624,7 +624,7 @@ <h1>Git Howto Index</h1>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-10-02 09:42:25 -0700
+Last updated 2024-10-04 15:34:15 -0700
 </div>
 </div>
 </body>

howto/keep-canonical-history-correct.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>Keep authoritative canonical history correct with git pull</h1>
 <div class="details">
-<span id="revdate">2024-10-02</span>
+<span id="revdate">2024-10-04</span>
 </div>
 </div>
 <div id="content">
@@ -705,7 +705,7 @@ <h1>Keep authoritative canonical history correct with git pull</h1>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-10-02 09:42:27 -0700
+Last updated 2024-10-04 15:34:50 -0700
 </div>
 </div>
 </body>

howto/maintain-git.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>How to maintain Git</h1>
 <div class="details">
-<span id="revdate">2024-10-02</span>
+<span id="revdate">2024-10-04</span>
 </div>
 </div>
 <div id="content">
@@ -531,7 +531,24 @@ <h2 id="_the_policy">The Policy</h2>
 </li>
 <li>
 <p><em>seen</em> branch is used to publish other proposed changes that do
-not yet pass the criteria set for <em>next</em> (see above).</p>
+not yet pass the criteria set for <em>next</em> (see above), but there
+is no promise that <em>seen</em> will contain everything.  A topic that
+had no reviewer reaction may not be picked up.</p>
+</li>
+<li>
+<p>A new topic will first get merged to <em>seen</em>, unless it is
+trivially correct and clearly urgent, in which case it may be
+directly merged to <em>next</em> or even to <em>master</em>.</p>
+</li>
+<li>
+<p>If a topic that was picked up to <em>seen</em> becomes and stays
+inactive for 3 calendar weeks without having seen a clear
+consensus that it is good enough to be moved to <em>next</em>, the
+topic may be discarded from <em>seen</em>.  Interested parties are
+still free to revive the topic.  For the purpose of this
+guideline, the definition of being "inactive" is that nobody
+has discussed the topic, no new iteration of the topic was
+posted, and no responses to the review comments were given.</p>
 </li>
 <li>
 <p>The tips of <em>master</em> and <em>maint</em> branches will not be rewound to
@@ -1242,7 +1259,7 @@ <h3 id="_preparing_a_merge_fix">Preparing a "merge-fix"</h3>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-10-02 09:42:27 -0700
+Last updated 2024-10-04 15:34:50 -0700
 </div>
 </div>
 </body>

howto/maintain-git.txt

@@ -67,7 +67,22 @@ the mailing list after each feature release is made:
    before getting merged to 'master'.
 
  - 'seen' branch is used to publish other proposed changes that do
-   not yet pass the criteria set for 'next' (see above).
+   not yet pass the criteria set for 'next' (see above), but there
+   is no promise that 'seen' will contain everything.  A topic that
+   had no reviewer reaction may not be picked up.
+
+   - A new topic will first get merged to 'seen', unless it is
+     trivially correct and clearly urgent, in which case it may be
+     directly merged to 'next' or even to 'master'.
+
+   - If a topic that was picked up to 'seen' becomes and stays
+     inactive for 3 calendar weeks without having seen a clear
+     consensus that it is good enough to be moved to 'next', the
+     topic may be discarded from 'seen'.  Interested parties are
+     still free to revive the topic.  For the purpose of this
+     guideline, the definition of being "inactive" is that nobody
+     has discussed the topic, no new iteration of the topic was
+     posted, and no responses to the review comments were given.
 
  - The tips of 'master' and 'maint' branches will not be rewound to
    allow people to build their own customization on top of them.

howto/new-command.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>How to integrate new subcommands</h1>
 <div class="details">
-<span id="revdate">2024-10-02</span>
+<span id="revdate">2024-10-04</span>
 </div>
 </div>
 <div id="content">
@@ -584,7 +584,7 @@ <h2 id="_integrating_a_command">Integrating a command</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-10-02 09:42:26 -0700
+Last updated 2024-10-04 15:34:48 -0700
 </div>
 </div>
 </body>

howto/rebase-from-internal-branch.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>How to rebase from an internal branch</h1>
 <div class="details">
-<span id="revdate">2024-10-02</span>
+<span id="revdate">2024-10-04</span>
 </div>
 </div>
 <div id="content">
@@ -656,7 +656,7 @@ <h1>How to rebase from an internal branch</h1>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-10-02 09:42:27 -0700
+Last updated 2024-10-04 15:34:50 -0700
 </div>
 </div>
 </body>

howto/rebuild-from-update-hook.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>How to rebuild from update hook</h1>
 <div class="details">
-<span id="revdate">2024-10-02</span>
+<span id="revdate">2024-10-04</span>
 </div>
 </div>
 <div id="content">
@@ -563,7 +563,7 @@ <h1>How to rebuild from update hook</h1>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-10-02 09:42:27 -0700
+Last updated 2024-10-04 15:34:50 -0700
 </div>
 </div>
 </body>

howto/recover-corrupted-blob-object.html

@@ -442,7 +442,7 @@
 <div id="header">
 <h1>How to recover a corrupted blob object</h1>
 <div class="details">
-<span id="revdate">2024-10-02</span>
+<span id="revdate">2024-10-04</span>
 </div>
 </div>
 <div id="content">
@@ -641,7 +641,7 @@ <h1>How to recover a corrupted blob object</h1>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2024-10-02 09:42:27 -0700
+Last updated 2024-10-04 15:34:49 -0700
 </div>
 </div>
 </body>