Autogenerated HTML docs for v2.52.0-209-ge85ae

Author: gitster

RelNotes/2.53.0.adoc

@@ -23,6 +23,9 @@ UI, Workflows & Features
  * "git fast-import" learns "--strip-if-invalid" option to drop
  invalid cryptographic signature from objects.
 
+ * The use of "revision" (a connected set of commits) has been
+ clarified in the "git replay" documentation.
+
 
 Performance, Internal Implementation, Development Support etc.
 --------------------------------------------------------------
@@ -135,6 +138,18 @@ Fixes since v2.52
  have been corrected.
  (merge df963f0df4 rs/config-set-multi-error-message-fix later to maint).
 
+ * "git replay" forgot to omit the "gpgsig-sha256" extended header
+ from the resulting commit the same way it omits "gpgsig", which has
+ been corrected.
+ (merge 9f3a115087 pw/replay-exclude-gpgsig-fix later to maint).
+
+ * A few tests have been updated to work under the shell compatible
+ mode of zsh.
+ (merge a92f243a94 bc/zsh-testsuite later to maint).
+
+ * The way patience diff finds LCS has been optimized.
+ (merge c7e3b8085b yc/xdiff-patience-optim later to maint).
+
  * Other code cleanup, docfix, build fix, etc.
  (merge 46207a54cc qj/doc-http-bad-want-response later to maint).
  (merge df90eccd93 kh/doc-commit-extra-references later to maint).

git-replay.adoc

@@ -9,12 +9,12 @@ git-replay - EXPERIMENTAL: Replay commits on a new base, works with bare repos t
 SYNOPSIS
 --------
 [verse]
-(EXPERIMENTAL!) 'git replay' ([--contained] --onto <newbase> | --advance <branch>) [--ref-action[=<mode>]] <revision-range>...
+(EXPERIMENTAL!) 'git replay' ([--contained] --onto <newbase> | --advance <branch>) [--ref-action[=<mode>]] <revision-range>
 
 DESCRIPTION
 -----------
 
-Takes ranges of commits and replays them onto a new location. Leaves
+Takes a range of commits and replays them onto a new location. Leaves
 the working tree and the index untouched. By default, updates the
 relevant references using an atomic transaction (all refs update or
 none). Use `--ref-action=print` to avoid automatic ref updates and
@@ -55,11 +55,10 @@ which uses the target only as a starting point without updating it.
 The default mode can be configured via the `replay.refAction` configuration variable.
 
 <revision-range>::
- Range of commits to replay. More than one <revision-range> can
- be passed, but in `--advance <branch>` mode, they should have
- a single tip, so that it's clear where <branch> should point
- to. See "Specifying Ranges" in linkgit:git-rev-parse[1] and the
- "Commit Limiting" options below.
+ Range of commits to replay; see "Specifying Ranges" in
+ linkgit:git-rev-parse[1]. In `--advance <branch>` mode, the
+ range should have a single tip, so that it's clear to which tip the
+ advanced <branch> should point.
 
 include::rev-list-options.adoc[]
 

git-replay.html

@@ -452,15 +452,15 @@ <h2 id="_name">NAME</h2>
 <h2id="_synopsis">SYNOPSIS</h2>
 <divclass="sectionbody">
 <divclass="verseblock">
-<preclass="content">(EXPERIMENTAL!) <em>git replay</em> ([--contained] --onto &lt;newbase&gt; | --advance &lt;branch&gt;) [--ref-action[=&lt;mode&gt;]] &lt;revision-range&gt;&#8230;&#8203;</pre>
+<preclass="content">(EXPERIMENTAL!) <em>git replay</em> ([--contained] --onto &lt;newbase&gt; | --advance &lt;branch&gt;) [--ref-action[=&lt;mode&gt;]] &lt;revision-range&gt;</pre>
 </div>
 </div>
 </div>
 <divclass="sect1">
 <h2id="_description">DESCRIPTION</h2>
 <divclass="sectionbody">
 <divclass="paragraph">
-<p>Takes ranges of commits and replays them onto a new location. Leaves
+<p>Takes a range of commits and replays them onto a new location. Leaves
 the working tree and the index untouched. By default, updates the
 relevant references using an atomic transaction (all refs update or
 none). Use <code>--ref-action=print</code> to avoid automatic ref updates and
@@ -522,11 +522,10 @@ <h2 id="_options">OPTIONS</h2>
 </dd>
 <dtclass="hdlist1">&lt;revision-range&gt;</dt>
 <dd>
-<p>Range of commits to replay. More than one &lt;revision-range&gt; can
-be passed, but in <code>--advance</code><em>&lt;branch&gt;</em> mode, they should have
-a single tip, so that it&#8217;s clear where &lt;branch&gt; should point
-to. See "Specifying Ranges" in <ahref="git-rev-parse.html">git-rev-parse(1)</a> and the
-"Commit Limiting" options below.</p>
+<p>Range of commits to replay; see "Specifying Ranges" in
+<ahref="git-rev-parse.html">git-rev-parse(1)</a>. In <code>--advance</code><em>&lt;branch&gt;</em> mode, the
+range should have a single tip, so that it&#8217;s clear to which tip the
+advanced &lt;branch&gt; should point.</p>
 </dd>
 </dl>
 </div>
@@ -1957,7 +1956,7 @@ <h2 id="_git">GIT</h2>
 </div>
 <divid="footer">
 <divid="footer-text">
-Last updated 2025-11-24 16:03:54 -0800
+Last updated 2025-12-09 07:59:24 +0900
 </div>
 </div>
 </body>