On Thu, Apr 23, 2020 at 08:47:00PM +0200, Ard Biesheuvel wrote: > On Thu, 23 Apr 2020 at 20:42, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > On Thu, Apr 23, 2020 at 09:18:15AM +0200, Ard Biesheuvel wrote: > > > FYI: you shouldn't cc stable@xxxxxxxxxxxxxxx directly on your patches, > > > or add the cc: line. Only patches that are already in Linus' tree > > > should be sent there. > > > > Not true at all, please read: > > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html > > for how to do this properly. Please do not spread incorrect > > information. > > > > And Jason did this properly, he put cc: stable@ in the s-o-b area and > > all is good, I will pick up this patch once it hits Linus's tree. > > > > And there is no problem actually sending the patch to stable@vger while > > under development like this, as it gives me a heads-up that something is > > coming, and is trivial to filter out. > > > > If you really want to be nice, you can just do: > > cc: stable@xxxxxxxxxx > > which goes to /dev/null on kernel.org, so no email will be sent to any > > list, but my scripts still pick it up. But no real need to do that, > > it's fine. > > > > OK, thanks for clearing this up. > > So does this mean you have stopped sending out 'formletter' > auto-replies for patches that were sent out to stable@xxxxxxxxxxxxxxx > directly, telling people not to do that? > I often leave stable@xxxxxxxxxxxxxxx in the email Cc list, and no one has ever complained. It's only sending patches directly "To:" stable@xxxxxxxxxxxxxxx that isn't allowed, except when actually sending out backports. If there were people who had an actual issue with Cc, then I think the rules would have changed long ago to using some other tag like Backport-to that doesn't get picked up by git send-email. - Eric
