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

From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Sep 8, 2025, 14:40 UTC
Message-ID: <ecdd1191-844b-47ca-9737-cc2ffb72b37d@app.fastmail.com>
In-Reply-To: <20250908043620.57848-3-siddharthasthana31@gmail.com>

On Mon, Sep 8, 2025, at 06:36, Siddharth Asthana wrote:

Show 14 quoted lines

>[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>...

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.

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