Git development
 help / color / mirror / Atom feed
From: Phillip Wood <phillip.wood123@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
	"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
	"Konstantin Ryabitsev" <mricon@kernel.org>
Subject: Re: [PATCH 00/11] sequencer: do not record dropped commits as rewritten
Date: Wed, 1 Jul 2026 14:31:04 +0100	[thread overview]
Message-ID: <dce74d17-eefd-40bb-82f3-f6b3179cc2b6@gmail.com> (raw)
In-Reply-To: <xmqqpl17rec3.fsf@gitster.g>

Hi Junio

On 30/06/2026 20:57, Junio C Hamano wrote:
> Phillip Wood <phillip.wood123@gmail.com> writes:
> 
> 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, I'll squash those locally and wait before resending

Phillip

> 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/
> 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 patch
> Looking for additional code-review trailers on lore.kernel.org
> Analyzing 0 code-review messages
> Checking attestation on all messages, may take a moment...
> ---
>    ✗ [PATCH] sequencer: Skip copying notes for commits that disappear during rebase
>      ✗ No key: openpgp/u.kleine-koenig@baylibre.com
>      ✗ BADSIG: DKIM/baylibre.com
>    ✓ [PATCH 1/11] t3400: restore coverage for note copying with apply backend
>      ✓ Signed: DKIM/gmail.com
>    ✓ [PATCH 3/11] sequencer: be more careful with external merge
>      ✓ Signed: DKIM/gmail.com
>    ✓ [PATCH 4/11] sequencer: never reschedule on failed commit
>      ✓ Signed: DKIM/gmail.com
>    ✓ [PATCH 5/11] sequencer: remove unnecessary "or" in pick_one_commit()
>      ✓ Signed: DKIM/gmail.com
>    ✓ [PATCH 6/11] sequencer: simplify handing of fixup with conflicts
>      ✓ Signed: DKIM/gmail.com
>    ✓ [PATCH 7/11] sequencer: remove unnecessary condition in pick_one_commit()
>      ✓ Signed: DKIM/gmail.com
>    ✓ [PATCH 8/11] sequencer: simplify pick_one_commit()
>      ✓ Signed: DKIM/gmail.com
>    ✓ [PATCH 9/11] sequencer: return early from pick_one_commit() on success
>      ✓ Signed: DKIM/gmail.com
>    ✓ [PATCH 10/11] sequencer: use an enum to represent result of picking a commit
>      ✓ Signed: DKIM/gmail.com
>    ✓ [PATCH 11/11] sequencer: do not record dropped commits as rewritten
>      ✓ Signed: DKIM/gmail.com
>    ERROR: missing [12/2]!
> ---
> Total patches: 11
> ---
> WARNING: Thread incomplete!
>   Link: https://patch.msgid.link/cover.1782833268.git.phillip.wood@dunelm.org.uk
> :
> 


  parent reply	other threads:[~2026-07-01 13:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16 17:40 [PATCH] sequencer: Skip copying notes for commits that disappear during rebase Uwe Kleine-König
2026-06-17 13:24 ` Junio C Hamano
2026-06-17 13:58   ` Uwe Kleine-König
2026-06-19 10:13     ` Phillip Wood
2026-06-19 13:01       ` Uwe Kleine-König
2026-06-30 15:28       ` [PATCH 00/11] sequencer: do not record dropped commits as rewritten Phillip Wood
2026-06-30 15:28         ` [PATCH 01/11] t3400: restore coverage for note copying with apply backend Phillip Wood
2026-06-30 15:28         ` [PATCH 02/11] sequencer: move definition of is_final_fixup() Phillip Wood
2026-06-30 15:28         ` [PATCH 03/11] sequencer: be more careful with external merge Phillip Wood
2026-06-30 15:28         ` [PATCH 04/11] sequencer: never reschedule on failed commit Phillip Wood
2026-06-30 15:28         ` [PATCH 05/11] sequencer: remove unnecessary "or" in pick_one_commit() Phillip Wood
2026-06-30 15:28         ` [PATCH 06/11] sequencer: simplify handing of fixup with conflicts Phillip Wood
2026-06-30 15:28         ` [PATCH 07/11] sequencer: remove unnecessary condition in pick_one_commit() Phillip Wood
2026-06-30 15:28         ` [PATCH 08/11] sequencer: simplify pick_one_commit() Phillip Wood
2026-07-06 11:06           ` Oswald Buddenhagen
2026-07-06 13:40             ` Phillip Wood
2026-06-30 15:28         ` [PATCH 09/11] sequencer: return early from pick_one_commit() on success Phillip Wood
2026-07-06 11:08           ` Oswald Buddenhagen
2026-06-30 15:29         ` [PATCH 10/11] sequencer: use an enum to represent result of picking a commit Phillip Wood
2026-07-06 11:12           ` Oswald Buddenhagen
2026-07-06 13:39             ` Phillip Wood
2026-06-30 15:29         ` [PATCH 11/11] sequencer: do not record dropped commits as rewritten Phillip Wood
2026-06-30 19:57         ` [PATCH 00/11] " Junio C Hamano
2026-07-01  6:00           ` Uwe Kleine-König
2026-07-01 13:29             ` Phillip Wood
2026-07-01 13:31           ` Phillip Wood [this message]
2026-07-01  9:38         ` Uwe Kleine-König
2026-07-01 13:37           ` Phillip Wood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dce74d17-eefd-40bb-82f3-f6b3179cc2b6@gmail.com \
    --to=phillip.wood123@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mricon@kernel.org \
    --cc=phillip.wood@dunelm.org.uk \
    --cc=u.kleine-koenig@baylibre.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox