On Tue, Sep 09, 2025 at 04:05:48PM +0200, Niklas Schnelle wrote: > On Tue, 2025-09-09 at 15:52 +0200, Benjamin Block wrote: > > On Thu, Sep 04, 2025 at 10:59:49AM +0200, Niklas Schnelle wrote: > > > Cc: stable@xxxxxxxxxxxxxxx # v6.2 > > > > Oh, I just noticed that Niklas. You added `Cc: stable@xxxxxxxxxxxxxxx`, but > > didn't actually include the address on the actual Cc of the mail? Was that > > intentional? > > > > Yes it was intentional. It's my understanding that the tag is enough > for the stable team to pick the commit up once it lands in Linus' tree. > And I do have stable@xxxxxxxxxxxxxxx explicitly ignored in b4 to > prevent accidentally sending not-yet-ready or internal patches there. Well, if it worked for you in the past, fair enough! I've always put it on Cc, hence why I was wondering :) > Sadly the docs don't spell out that Ccing the list isn't needed though > I feel like it is implied by the "Cc: stable@xxxxxxxxxx" variant where > the docs mention that mails send by git send-email will go nowhere. I think that part only means that address is basically /dev/null, even if a mail is sent there. `git send-email` will try to include any address on such a Cc tag by default (https://git-scm.com/docs/git-send-email#Documentation/git-send-email.txt---suppress-cccategory) -- Best Regards, Benjamin Block / Linux on IBM Z Kernel Development IBM Deutschland Research & Development GmbH / https://www.ibm.com/privacy Vors. Aufs.-R.: Wolfgang Wendt / Geschäftsführung: David Faller Sitz der Ges.: Böblingen / Registergericht: AmtsG Stuttgart, HRB 243294
