Re: [PATCH v5 00/14] Introduce new `git replay` command
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Nov 8, 2023, 12:25 UTC
- Message-ID
- <1f2959d7-6e0f-bc8e-8341-56a1221dd48d@gmx.de>
- In-Reply-To
- <CAP8UFD09dZbrbebRFZvarY71q5Vc0YBfRQHbTg7A3H-qM2g8fg@mail.gmail.com>
Hi Christian,
On Thu, 2 Nov 2023, Christian Couder wrote:
Show 16 quoted lines
> On Thu, Oct 26, 2023 at 3:44 PM Johannes Schindelin > <Johannes.Schindelin@gmx.de> wrote: > > > 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.
Thank you for putting in the effort. I appreciate it very much.
Ciao, Johannes