Re: [PATCH 00/11] sequencer: do not record dropped commits as rewritten
From: Phillip Wood <hidden>
Date: 2026-07-01 13:29:39
On 01/07/2026 07:00, Uwe Kleine-König wrote:
Hello, On Tue, Jun 30, 2026 at 12:57:32PM -0700, Junio C Hamano wrote:quoted
A tangent (I Cc'ed Konstantin for this), but $ b4 am -o- '[ref]' >b4am.mbx failed to produce a usable mailbox. It somehow did not think [2/11] existed.FTR: The mail is on lore.kernel.org. Also to yield a usable mailbox my patch shouldn't be included.
Sorry I had intended to send these as v2 to avoid any confusion, but I forgot about that when I actually came to send them. Thanks Phillip
quoted
I manually examined the References and In-Reply-To headers of that particular message and compared them with those from other messages but did not find anything suspicious X-<.quoted
I have a bunch of typofixes queued on top of these 11 patches (made with "git commit --fixup reword:<sha1>"); please double check when you reroll after seeing more substantial reviews than mere typofixes, possibly from others. Thanks. Here is the transcript of failed b4 am invocation. ---- >8 ---- Looking up https://lore.kernel.org/all/cover.1782833268.git.phillip.wood@dunelm.org.uk/ (local) Grabbing thread from lore.kernel.org/all/cover.1782833268.git.phillip.wood@dunelm.org.uk/t.mbox.gz Analyzing 17 messages in the thread WARNING: duplicate messages found at index 1 Subject 1: sequencer: Skip copying notes for commits that disappear during rebase Subject 2: t3400: restore coverage for note copying with apply backend 2 is not a reply... assume additional patchI think here is the origin of the problem. It guesses that the t3400 should be added, and it takes the place of Phillip's second patch.quoted
ERROR: missing [12/2]!This is irritating, I would have expected "[2/12]" here? b4 am --no-parent cover.1782833268.git.phillip.wood@dunelm.org.uk works fine for me. Best regards Uwe