From: Christian Couder <christian.couder@gmail.com>
Date: Thu, 16 Nov 2023 08:52:24 GMT
Subject: Re: [PATCH v6 00/14] Introduce new `git replay` command
Message-ID: <CAP8UFD2hB5j2rZ-+WTXgju4mf58HGtEJR87LB08g3Hu3-G2joA@mail.gmail.com>
In-Reply-To: <0ddca907-6e64-b684-2e08-c7e95e737a3c@gmx.de>

Hi Dscho,

On Thu, Nov 16, 2023 at 9:45 AM Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> On Wed, 15 Nov 2023, Christian Couder wrote:

> > I have fixed that in the v7 I just sent with the following:
> >
> > +SYNOPSIS
> > +--------
> > +[verse]
> > +'git replay' --onto <newbase> <oldbase> <branch> # EXPERIMENTAL
>
> I still think that the following would serve us better:
>
>         [verse]
>         (EXPERIMENTAL!) 'git replay' --onto <newbase> <oldbase> <branch>
>
> But if nobody else feels as strongly, I won't bring this up again.

For the tests to pass, the SYNOPSIS should be the same as the first
line of the `git replay -h` output. After this series it is:

usage: git replay ([--contained] --onto <newbase> | --advance
<branch>) <revision-range>... # EXPERIMENTAL

As the usage is supposed to describe how the command should be used, I
think it makes sense for "EXPERIMENTAL" to be in a shell comment after
the command.

Thanks,
Christian.