Re: [PATCH 2/2] replay: document --update-refs and --batch options

From: Siddharth Asthana <siddharthasthana31@gmail.com>
Date: Sep 9, 2025, 07:06 UTC
Message-ID: <d070bbe1-8142-4811-b8ec-6d705b969381@gmail.com>
In-Reply-To: <ecdd1191-844b-47ca-9737-cc2ffb72b37d@app.fastmail.com>

On 08/09/25 20:10, Kristoffer Haugsbakk wrote:

Show 15 quoted lines

> On Mon, Sep 8, 2025, at 06:36, Siddharth Asthana wrote:
>> [snip]
>> diff --git a/Documentation/git-replay.adoc
>> b/Documentation/git-replay.adoc
>> index 0b12bf8aa4..cc9f868c2f 100644
>> --- a/Documentation/git-replay.adoc
>> +++ b/Documentation/git-replay.adoc
>> @@ -9,16 +9,17 @@ git-replay - EXPERIMENTAL: Replay commits on a new
>> base, works with bare repos t
>>   SYNOPSIS
>>   --------
>>   [verse]
>> -(EXPERIMENTAL!) 'git replay' ([--contained] --onto <newbase> |
>> --advance <branch>) <revision-range>...
>> +(EXPERIMENTAL!) 'git replay' ([--contained] --onto <newbase> | --advance <branch>) [--update | --update-refs [--batch]] <revision-range>...

Hi Kristoffer,

> Another downside of making a separate commit for the documentation is
> that now `t/t0450-txt-doc-vs-help.sh` will likely fail for your first
> commit.  One of the tests makes sure that the synopsis and the `.adoc`
> is in synch.

You are right, I will combine the documentation with the implementation patch in v2 to avoid the test failure.

Thanks, Siddharth

>
>>   DESCRIPTION
>>   -----------
>> [snip]