Autogenerated HTML docs for v2.49.0-rc0-18-gcb0ae

Author: gitster

Diff for: BreakingChanges.adoc

@@ -169,8 +169,8 @@ started to migrate away from ".git/remotes/" in favor of config-based remotes,
 and we have marked the directory as legacy in 3d3d282146 (Documentation:
 Grammar correction, wording fixes and cleanup, 2011-08-23)
 +
-As our documentation mentions, these directories are not to be found in modern
-repositories at all and most users aren't even aware of these mechanisms. They
+As our documentation mentions, these directories are unlikely to be used in
+modern repositories and most users aren't even aware of these mechanisms. They
 have been deprecated for almost 20 years and 14 years respectively, and we are
 not aware of any active users that have complained about this deprecation.
 Furthermore, the ".git/branches/" directory is nowadays misleadingly named and

Diff for: RelNotes/2.49.0.adoc

@@ -38,6 +38,17 @@ UI, Workflows & Features
  * The documentation of "git commit" and "git rebase" now refer to
    commit titles as such, not "subject".
 
+ * The value of "uname -s" is by default sent over the wire as a part
+   of the "version" capability.
+
+ * "git refs migrate" can optionally be told not to migrate the reflog.
+
+ * The netrc support (via the cURL library) for the HTTP transport has
+   been re-enabled.
+
+ * Removal of ".git/branches" and ".git/remotes" support in the
+   BreakingChanges document has been further clarified.
+
 
 Performance, Internal Implementation, Development Support etc.
 --------------------------------------------------------------
@@ -220,6 +231,16 @@ Fixes since v2.48
    default target (which happens to be "all") upfront.
    (merge 5309c1e9fb ad/set-default-target-in-makefiles later to maint).
 
+ * "git check-mailmap" used to segfault when queried without human
+   readable name.
+   (merge bb60c52131 jk/check-mailmap-wo-name-fix later to maint).
+
+ * Support for renaming of symbolic links on Windows has been improved.
+
+ * "git rebase -i" failed to allow rewording an empty commit that has
+   been fast-forwarded.
+   (merge af8fc7be10 pw/rebase-i-ff-empty-commit later to maint).
+
  * Other code cleanup, docfix, build fix, etc.
    (merge ddb5287894 jk/t7407-use-test-grep later to maint).
    (merge 21e1b44865 aj/difftool-config-doc-fix later to maint).

Diff for: git-refs.adoc

@@ -8,9 +8,9 @@ git-refs - Low-level access to refs
 
 SYNOPSIS
 --------
-[verse]
-'git refs migrate' --ref-format=<format> [--dry-run]
-'git refs verify' [--strict] [--verbose]
+[synopsis]
+git refs migrate --ref-format=<format> [--no-reflog] [--dry-run]
+git refs verify [--strict] [--verbose]
 
 DESCRIPTION
 -----------
@@ -43,6 +43,11 @@ include::ref-storage-format.adoc[]
 	can be used to double check that the migration works as expected before
 	performing the actual migration.
 
+--reflog::
+--no-reflog::
+	Choose between migrating the reflog data to the new backend,
+	and discarding them.  The default is "--reflog", to migrate.
+
 The following options are specific to 'git refs verify':
 
 --strict::

Diff for: git-refs.html

@@ -452,8 +452,8 @@ <h2 id="_name">NAME</h2>
 <h2 id="_synopsis">SYNOPSIS</h2>
 <div class="sectionbody">
 <div class="verseblock">
-<pre class="content"><em>git refs migrate</em> --ref-format=&lt;format&gt; [--dry-run]
-<em>git refs verify</em> [--strict] [--verbose]</pre>
+<pre class="content"><code>git</code> <code>refs</code> <code>migrate</code> <code>--ref-format=</code><em>&lt;format&gt;</em> [<code>--no-reflog</code>] [<code>--dry-run</code>]
+<code>git</code> <code>refs</code> <code>verify</code> [<code>--strict</code>] [<code>--verbose</code>]</pre>
 </div>
 </div>
 </div>
@@ -513,6 +513,12 @@ <h2 id="_options">OPTIONS</h2>
 can be used to double check that the migration works as expected before
 performing the actual migration.</p>
 </dd>
+<dt class="hdlist1">--reflog</dt>
+<dt class="hdlist1">--no-reflog</dt>
+<dd>
+<p>Choose between migrating the reflog data to the new backend,
+and discarding them.  The default is "--reflog", to migrate.</p>
+</dd>
 </dl>
 </div>
 <div class="paragraph">
@@ -569,7 +575,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-02-14 21:38:14 -0800
+Last updated 2025-02-27 16:06:53 -0800
 </div>
 </div>
 </body>

Diff for: gitprotocol-v2.adoc

@@ -184,9 +184,13 @@ form `agent=X`) to notify the client that the server is running version
 the `agent` capability with a value `Y` (in the form `agent=Y`) in its
 request to the server (but it MUST NOT do so if the server did not
 advertise the agent capability). The `X` and `Y` strings may contain any
-printable ASCII characters except space (i.e., the byte range 32 < x <
-127), and are typically of the form "package/version" (e.g.,
-"git/1.8.3.1"). The agent strings are purely informative for statistics
+printable ASCII characters except space (i.e., the byte range 33 <= x <=
+126), and are typically of the form "package/version-os" (e.g.,
+"git/1.8.3.1-Linux") where `os` is the operating system name (e.g.,
+"Linux"). `X` and `Y` can be configured using the GIT_USER_AGENT
+environment variable and it takes priority. The `os` is
+retrieved using the 'sysname' field of the `uname(2)` system call
+or its equivalent. The agent strings are purely informative for statistics
 and debugging purposes, and MUST NOT be used to programmatically assume
 the presence or absence of particular features.
 

Diff for: gitprotocol-v2.html

@@ -706,9 +706,13 @@ <h3 id="_agent">agent</h3>
 the <code>agent</code> capability with a value <code>Y</code> (in the form <code>agent=Y</code>) in its
 request to the server (but it MUST NOT do so if the server did not
 advertise the agent capability). The <code>X</code> and <code>Y</code> strings may contain any
-printable ASCII characters except space (i.e., the byte range 32 &lt; x &lt;
-127), and are typically of the form "package/version" (e.g.,
-"git/1.8.3.1"). The agent strings are purely informative for statistics
+printable ASCII characters except space (i.e., the byte range 33 &#8656; x &#8656;
+126), and are typically of the form "package/version-os" (e.g.,
+"git/1.8.3.1-Linux") where <code>os</code> is the operating system name (e.g.,
+"Linux"). <code>X</code> and <code>Y</code> can be configured using the GIT_USER_AGENT
+environment variable and it takes priority. The <code>os</code> is
+retrieved using the <em>sysname</em> field of the <code>uname</code>(<code>2</code>) system call
+or its equivalent. The agent strings are purely informative for statistics
 and debugging purposes, and MUST NOT be used to programmatically assume
 the presence or absence of particular features.</p>
 </div>
@@ -1526,7 +1530,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-02-14 21:38:14 -0800
+Last updated 2025-02-27 16:06:53 -0800
 </div>
 </div>
 </body>