Re: [PATCH v3 11/15] replay: use standard revision ranges

From: Dragan Simic <dsimic@manjaro.org>
Date: Sep 7, 2023, 21:02 UTC
Message-ID: <f412f62bf830b38a296b59ac3470099a@manjaro.org>
In-Reply-To: <CAP8UFD1_67rNke1y-GV7qX46GXQkNJzw7fXfK=kkUjc-jb5S_g@mail.gmail.com>

On 2023-09-07 10:32, Christian Couder wrote:

Show 21 quoted lines

> On Thu, Jun 22, 2023 at 12:03 PM Toon Claes <toon@iotcl.com> wrote:
>> 
>> Christian Couder <christian.couder@gmail.com> writes:
>> 
>> > +DESCRIPTION
>> > +-----------
>> > +
>> > +Takes a range of commits, and replays them onto a new location.  Does
>> > +not touch the working tree or index, and does not update any
>> > +references.  However, the output of this command is meant to be used
>> 
>> Small suggestion here:
>> 
>> Takes a range of commits, and replays them onto a new location.  Does
>> neither touch the working tree nor index, and does not update any
>> references.
> 
> I am not a native speaker, so I am not sure what's best here. I find
> your suggestion a bit less clear though, so until a native speaker
> agrees with it or maybe finds something even better, I prefer to leave
> it as-is.

I'm also not a native English speaker, but I spent about 2.5 years contributing a whole lot to English Wikipedia, so I'd dare to say I've honed my English skills rather well. Thus, here's my take on this:

     Takes a range of commits and replays them onto a new location.
     Leaves the working tree and the index untouched, and updates no
     references.  The output of this command is to be used...

This is written in a concise yet slightly imperative way, which should be suitable for the purpose. I hope you agree.