tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
* b4: message-id from deps added to cc list?
@ 2024-08-05 23:56 Kevin Hilman
  2024-08-07 14:22 ` Konstantin Ryabitsev
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: Kevin Hilman @ 2024-08-05 23:56 UTC (permalink / raw)
  To: tools

Hello,

I've been happily using b4 for awhile to collect and apply patches
locally, but finally starting using it to manage & send patches.

First, thank you for all the work on b4.  It's a major improvment to my
workflow!

I'm using b4 from the stable-0.14.y branch, and I noticed one pecuilar
thing on the series I just sent[1], and that is the message-id I put in
the deps (using `b4 prep --edit-deps`) correctly showed up as
prerequisite-message-id, but for some reason, it also ended up in the Cc
list, leading to bounces for all mails in the thread.

I double-checked managed cover letter (using `b4 prep --edit-cover`) and
it is definitely *not* listed as a Cc.

Looking back, I do see it in the Cc list when I `b4 send --dry-run` but
I didn't notice it before sending. :(

How is that getting into the cc list?  Is it grabbing this part of the
cover letter:

> This series depends on the support for the new TI SCI APIs here:
> https://lore.kernel.org/r/20240801195422.2296347-1-msp@baylibre.com

and assuming that's an email address and automatically adding it to the
cc list?

Thanks,

Kevin

[1] https://lore.kernel.org/linux-pm/20240805-lpm-v6-10-constraints-pmdomain-v1-0-d186b68ded4c@baylibre.com

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2024-09-06 14:25 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-08-05 23:56 b4: message-id from deps added to cc list? Kevin Hilman
2024-08-07 14:22 ` Konstantin Ryabitsev
2024-08-07 14:23 ` Kernel.org Bugbot
2024-08-19 23:46 ` Kevin Hilman
2024-09-06 14:25 ` Kernel.org Bugbot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).