On 12/1/22 15:16, Konstantin Ryabitsev wrote:
On Thu, Dec 01, 2022 at 02:34:41PM +0100, Javier Martinez Canillas wrote:
Konstantin,
Can you add a rule in b4 to exclude stable@xxxxxxxxxxxxxxx
(stable@xxxxxxxxxx as well?) from getting the whole patchset?
stable@xxxxxxxxxx is a pipe to /dev/null so that's not needed to be
messed with.
As for this needing special casing in b4, it's rare that you send out a
patch series and only want 1 or 2 of them in stable, right?
Not really, it's very common for a patch-series to contain fixes (that could
go to stable if applicable) and change that are not suitable for stable. The
problem as Noralf mentioned is that the b4 tool doesn't seem to allow Cc'ing
individual patches to different recipients, and everyone get the whole set.
So either b4 needs to have this support, exclude stable@xxxxxxxxxxxxxxx when
sending a set or stable@xxxxxxxxxxxxxxx ignore patches without a Fixes: tag.
I think what I can do is a special logic for Cc: trailers:
- Any Cc: trailers we find in the cover letter receive the entire series
- Any Cc: trailers in individual patches only receive these individual patches
I usually do that with git send-email and a custom --cc-cmd script, but
additionally it sends the cover letter also to everyone that's on any
individual patch's Cc, so everyone gets at least the cover letter +
their specific patch(es).
But that extra logic could be optional.
Thank you for being patient -- we'll get this right, I promise.
-K
