Den 01.12.2022 15.16, skrev Konstantin Ryabitsev: > 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 > That should cover my use cases. I can now do 'b4 prep --auto-to-cc' and then trim down the cc list in the cover letter if necessary. > Thank you for being patient -- we'll get this right, I promise. > Thanks for getting it right. b4 can replace parts of my own tooling and do it smoother so I think I'll continue to use it. Noralf.
