Re: [PATCH v5 00/14] Introduce new `git replay` command

From: Christian Couder <christian.couder@gmail.com>
Date: Nov 2, 2023, 14:48 UTC
Message-ID: <CAP8UFD38KEdpArdixVHpTFGF__G89s_sMUHa+gmWoLULv+CvJw@mail.gmail.com>
In-Reply-To: <CABPp-BGCzxL-kpOvZzWRTJcx2v18QHm5ev8bFv7bm0dyNqhKug@mail.gmail.com>

On Sun, Oct 29, 2023 at 7:00 AM Elijah Newren <newren@gmail.com> wrote:

> On Tue, Oct 10, 2023 at 5:39 AM Christian Couder
> <christian.couder@gmail.com> wrote:

Show 8 quoted lines

> >     @@ Documentation/git-replay.txt (new)
> >      +
> >      +NAME
> >      +----
> >     -+git-replay - Replay commits on a different base, without touching working tree
> >     ++git-replay - Replay commits on a new base, works on bare repos too
>
> really minor point: "works on" or "works in" or "works with" ?

I have changed it to "works with", I hope it sounds better. Also I forgot to talk about this change in the cover letter, sorry about that.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.