Autogenerated HTML docs for v2.51.0-244-g92c87

Author: gitster

RelNotes/2.52.0.adoc

@@ -17,6 +17,9 @@ UI, Workflows & Features
  * A new command "git last-modified" has been added to show the closest
  ancestor commit that touched each path.
 
+ * "git refs exists" that works like "git show-ref --exists" has been
+ added.
+
 
 Performance, Internal Implementation, Development Support etc.
 --------------------------------------------------------------
@@ -47,6 +50,11 @@ Performance, Internal Implementation, Development Support etc.
  hash function implementation used to hash lines have been updated
  to the one used for ELF symbol lookup by Glibc.
 
+ * Instead of scanning for the remaining items to see if there are
+ still commits to be explored in the queue, use khash to remember
+ which items are still on the queue (an unacceptable alternative is
+ to reserve one object flag bits).
+
 
 Fixes since v2.51
 -----------------
@@ -151,6 +159,11 @@ including security updates, are included in this release.
  this.
  (merge 681f26bccc ds/ls-files-lazy-unsparse later to maint).
 
+ * Windows "real-time monitoring" interferes with the execution of
+ tests and affects negatively in both correctness and performance,
+ which has been disabled in Gitlab CI.
+ (merge 608cf5b793 ps/gitlab-ci-disable-windows-monitoring later to maint).
+
  * Other code cleanup, docfix, build fix, etc.
  (merge 823d537fa7 kh/doc-git-log-markup-fix later to maint).
  (merge cf7efa4f33 rj/t6137-cygwin-fix later to maint).
@@ -164,3 +177,8 @@ including security updates, are included in this release.
  (merge 374579c6d4 kh/doc-interpret-trailers-markup-fix later to maint).
  (merge 44dce6541c kh/doc-config-typofix later to maint).
  (merge 785628b173 js/doc-sending-patch-via-thunderbird later to maint).
+ (merge e5c27bd3d8 je/doc-add later to maint).
+ (merge 13296ac909 ps/object-store-midx-dedup-info later to maint).
+ (merge 2f4bf83ffc km/alias-doc-markup-fix later to maint).
+ (merge b0d97aac19 kh/doc-markup-fixes later to maint).
+ (merge f9a6705d9a tc/t0450-harden later to maint).

fetch-options.adoc

@@ -2,7 +2,7 @@
 --no-all::
  Fetch all remotes, except for the ones that has the
 `remote.<name>.skipFetchAll` configuration variable set.
- This overrides the configuration variable fetch.all`.
+ This overrides the configuration variable `fetch.all`.
 
 -a::
 --append::

git-add.adoc

@@ -16,18 +16,18 @@ git add [--verbose | -v] [--dry-run | -n] [--force | -f] [--interactive | -i] [-
 
 DESCRIPTION
 -----------
-This command updates the index using the current content found in
-the working tree, to prepare the content staged for the next commit.
-It typically adds the current content of existing paths as a whole,
-but with some options it can also be used to add content with
-only part of the changes made to the working tree files applied, or
-remove paths that do not exist in the working tree anymore.
-
-The "index" holds a snapshot of the content of the working tree, and it
-is this snapshot that is taken as the contents of the next commit. Thus
-after making any changes to the working tree, and before running
-the commit command, you must use the `add` command to add any new or
-modified files to the index.
+Add contents of new or changed files to the index. The "index" (also
+known as the "staging area") is what you use to prepare the contents of
+the next commit.
+
+When you run `git commit` without any other arguments, it will only
+commit staged changes. For example, if you've edited `file.c` and want
+to commit your changes to that file, you can run:
+
+ git add file.c
+ git commit
+
+You can also add only part of your changes to a file with `git add -p`.
 
 This command can be performed multiple times before a commit. It only
 adds the content of the specified file(s) at the time the add command is
@@ -37,12 +37,10 @@ you must run `git add` again to add the new content to the index.
 The `git status` command can be used to obtain a summary of which
 files have changes that are staged for the next commit.
 
-The `git add` command will not add ignored files by default. If any
-ignored files were explicitly specified on the command line, `git add`
-will fail with a list of ignored files. Ignored files reached by
-directory recursion or filename globbing performed by Git (quote your
-globs before the shell) will be silently ignored. The `git add` command can
-be used to add ignored files with the `-f` (force) option.
+The `git add` command will not add ignored files by default. You can
+use the `--force` option to add ignored files. If you specify the exact
+filename of an ignored file, `git add` will fail with a list of ignored
+files. Otherwise it will silently ignore the file.
 
 Please see linkgit:git-commit[1] for alternative ways to add content to a
 commit.

git-add.html

@@ -464,19 +464,23 @@ <h2 id="_synopsis">SYNOPSIS</h2>
 <h2id="_description">DESCRIPTION</h2>
 <divclass="sectionbody">
 <divclass="paragraph">
-<p>This command updates the index using the current content found in
-the working tree, to prepare the content staged for the next commit.
-It typically adds the current content of existing paths as a whole,
-but with some options it can also be used to add content with
-only part of the changes made to the working tree files applied, or
-remove paths that do not exist in the working tree anymore.</p>
+<p>Add contents of new or changed files to the index. The "index" (also
+known as the "staging area") is what you use to prepare the contents of
+the next commit.</p>
 </div>
 <divclass="paragraph">
-<p>The "index" holds a snapshot of the content of the working tree, and it
-is this snapshot that is taken as the contents of the next commit. Thus
-after making any changes to the working tree, and before running
-the commit command, you must use the <code>add</code> command to add any new or
-modified files to the index.</p>
+<p>When you run <code>git</code><code>commit</code> without any other arguments, it will only
+commit staged changes. For example, if you&#8217;ve edited <code>file.c</code> and want
+to commit your changes to that file, you can run:</p>
+</div>
+<divclass="literalblock">
+<divclass="content">
+<pre>git add file.c
+git commit</pre>
+</div>
+</div>
+<divclass="paragraph">
+<p>You can also add only part of your changes to a file with <code>git</code><code>add</code><code>-p</code>.</p>
 </div>
 <divclass="paragraph">
 <p>This command can be performed multiple times before a commit. It only
@@ -489,12 +493,10 @@ <h2 id="_description">DESCRIPTION</h2>
 files have changes that are staged for the next commit.</p>
 </div>
 <divclass="paragraph">
-<p>The <code>git</code><code>add</code> command will not add ignored files by default. If any
-ignored files were explicitly specified on the command line, <code>git</code><code>add</code>
-will fail with a list of ignored files. Ignored files reached by
-directory recursion or filename globbing performed by Git (quote your
-globs before the shell) will be silently ignored. The <code>git</code><code>add</code> command can
-be used to add ignored files with the <code>-f</code> (force) option.</p>
+<p>The <code>git</code><code>add</code> command will not add ignored files by default. You can
+use the <code>--force</code> option to add ignored files. If you specify the exact
+filename of an ignored file, <code>git</code><code>add</code> will fail with a list of ignored
+files. Otherwise it will silently ignore the file.</p>
 </div>
 <divclass="paragraph">
 <p>Please see <ahref="git-commit.html">git-commit(1)</a> for alternative ways to add content to a
@@ -1043,7 +1045,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <divid="footer">
 <divid="footer-text">
-Last updated 2025-08-04 09:35:46 -0700
+Last updated 2025-09-12 12:13:52 -0700
 </div>
 </div>
 </body>

git-config.html

@@ -2041,8 +2041,8 @@ <h3 id="_variables">Variables</h3>
 <li>
 <p>A convenient way to deal with this is to write your script
 operations in an inline function that is then called with any
-arguments from the command-line. For example `alias.cmd = "!c(){
-echo $1 | grep $2 }; c" will correctly execute the prior example.</p>
+arguments from the command-line. For example <code>alias.cmd</code><code>=</code> "!c(){
+<code>echo</code><code>$1</code> | <code>grep</code><code>$2</code> }; <code>c</code>" will correctly execute the prior example.</p>
 </li>
 <li>
 <p>Setting <code>GIT_TRACE=1</code> can help you debug the command being run for

git-fast-import.adoc

@@ -647,7 +647,7 @@ External data format::
 +
 Here usually `<dataref>` must be either a mark reference (`:<idnum>`)
 set by a prior `blob` command, or a full 40-byte SHA-1 of an
-existing Git blob object. If `<mode>` is `040000`` then
+existing Git blob object. If `<mode>` is `040000` then
 `<dataref>` must be the full 40-byte SHA-1 of an existing
 Git tree object or a mark reference set with `--import-marks`.
 

git-fast-import.html

@@ -1262,7 +1262,7 @@ <h4 id="_filemodify"><code>filemodify</code></h4>
 <divclass="paragraph">
 <p>Here usually <em>&lt;dataref&gt;</em> must be either a mark reference (<code>:</code><em>&lt;idnum&gt;</em>)
 set by a prior <code>blob</code> command, or a full 40-byte SHA-1 of an
-existing Git blob object. If <em>&lt;mode&gt;</em> is <code>040000</code>` then
+existing Git blob object. If <em>&lt;mode&gt;</em> is <code>040000</code> then
 <em>&lt;dataref&gt;</em> must be the full 40-byte SHA-1 of an existing
 Git tree object or a mark reference set with <code>--import-marks</code>.</p>
 </div>
@@ -2609,7 +2609,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <divid="footer">
 <divid="footer-text">
-Last updated 2025-08-25 14:46:08 -0700
+Last updated 2025-09-12 12:13:52 -0700
 </div>
 </div>
 </body>

git-fetch.html

@@ -504,7 +504,7 @@ <h2 id="_options">OPTIONS</h2>
 <dd>
 <p>Fetch all remotes, except for the ones that has the
 <code>remote.</code><em>&lt;name&gt;</em><code>.skipFetchAll</code> configuration variable set.
-This overrides the configuration variable fetch.all`.</p>
+This overrides the configuration variable <code>fetch.all</code>.</p>
 </dd>
 <dtclass="hdlist1">-a</dt>
 <dtclass="hdlist1">--append</dt>

git-multi-pack-index.adoc

@@ -29,7 +29,7 @@ OPTIONS
 --no-progress::
  Turn progress on/off explicitly. If neither is specified, progress is
  shown if standard error is connected to a terminal. Supported by
- sub-commands `write`, `verify`, `expire`, and `repack.
+ sub-commands `write`, `verify`, `expire`, and `repack`.
 
 The following subcommands are available:
 

git-multi-pack-index.html

@@ -483,7 +483,7 @@ <h2 id="_options">OPTIONS</h2>
 <dd>
 <p>Turn progress on/off explicitly. If neither is specified, progress is
 shown if standard error is connected to a terminal. Supported by
-sub-commands <code>write</code>, <code>verify</code>, <code>expire</code>, and `repack.</p>
+sub-commands <code>write</code>, <code>verify</code>, <code>expire</code>, and <code>repack</code>.</p>
 </dd>
 </dl>
 </div>
@@ -674,7 +674,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <divid="footer">
 <divid="footer-text">
-Last updated 2025-08-25 14:46:08 -0700
+Last updated 2025-09-12 12:13:52 -0700
 </div>
 </div>
 </body>