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

From: Christian Couder <christian.couder@gmail.com>
Date: Nov 2, 2023, 15:06 UTC
Message-ID: <CAP8UFD09dZbrbebRFZvarY71q5Vc0YBfRQHbTg7A3H-qM2g8fg@mail.gmail.com>
In-Reply-To: <bd872b81-80a9-5e4e-dcb6-faebc9671848@gmx.de>

Hi Dscho and Elijah,

On Thu, Oct 26, 2023 at 3:44 PM Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 7 quoted lines

> In addition, I am still a bit uneasy with introducing both the manual page
> and the test script in this commit (see my comments in
> https://lore.kernel.org/git/03460733-0219-c648-5757-db1958f8042e@gmx.de/).
> It would be better to uphold our high standard and introduce scaffolds for
> both files in the first commit, then populate the file contents
> incrementally in the same the patches that introduce the corresponding
> options/features/changes.

I have tried to improve on that in the v6 I just sent, but there are many patches implementing changes in behavior that I think weren't worth documenting and testing in `test-tool fast-rebase` (which had no doc and no test) and that aren't worth documenting and testing specifically in `git replay` either.

Thanks!