From: Weijie Yuan <wy@wyuan.org>
To: Mostafa Saleh <smostafa@google.com>
Cc: tools@kernel.org
Subject: Re: [PATCH b4] b4: Ignore Signed-off-by trailers in follow-up replies
Date: Mon, 17 Aug 2026 15:14:07 +0800 [thread overview]
Message-ID: <aoK0v8bbaa5rHjbS@wyuan.org> (raw)
In-Reply-To: <20260808164708.1084648-1-smostafa@google.com>
On Sat, Aug 08, 2026 at 04:47:08PM +0000, Mostafa Saleh wrote:
> When someone replies to a patch thread, sometimes they include a
> Signed-off-by trailer (for example, when providing inline diffs or
> snippets in a reply). Currently, b4 am/shazam collect these tags
> from replies and append them to the main patch's trailers.
>
> I am not aware of any use case when collecting the Signed-off-by
> is needed, so drop it in this case.
>
> Assisted-by: Gemini:gemini-3.1-pro-preview
> Signed-off-by: Mostafa Saleh <smostafa@google.com>
>
> ---
> I hit this when using:
> b4 shazam -v1 https://lore.kernel.org/all/20260806150105.4010701-1-smostafa@google.com/
>
> It collected the tag from Marc's patch in my patch as in:
> https://lore.kernel.org/all/20260808085824.732659-4-smostafa@google.com/
> Which is wrong.
I have a simailar case?
My reply [1] contains a standard template of a commit message for
Chinese translation patches with a sample Signed-off-by in it.
So when using 'b4 am/shazam', the sample Signed-off-by would be added as
one trailer. I was curious and spent some time to figure out where the
Sob exactly come from within that quite large series, since that sample
name/maintainer didn't show up in that conversation at all. ;-)
And I am also not aware of any use case when collecting the Signed-off-by
is needed, though I'm quite new in this community without much
experience.
Thanks,
Weijie
[1] https://lore.kernel.org/linux-doc/amDdPZ4SqBNg1kBa@wyuan.org/
prev parent reply other threads:[~2026-08-17 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 16:47 [PATCH b4] b4: Ignore Signed-off-by trailers in follow-up replies Mostafa Saleh
2026-08-17 7:14 ` Weijie Yuan [this message]
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=aoK0v8bbaa5rHjbS@wyuan.org \
--to=wy@wyuan.org \
--cc=smostafa@google.com \
--cc=tools@kernel.org \
/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