On Thu, Mar 30, 2023 at 07:50:11PM +0000, Dexuan Cui wrote:
quoted
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
quoted
...
e70af8d040d2 has a Fixes tag. Not sure why it's not automatically
backported.
Because "Fixes:" is not the flag that we are sure to trigger off of.
Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
Thanks, I just read this again to refresh my memory :-)
I remember Sasha has an AI algorithm to pick up patches into the stable
tree and a "Fixes" tag should be a strong indicator.
Yes, we have to rely on "hints" like that due to maintainers not wanting
to put any cc: stable tags for many subsystems so we have to dig them
out somehow.
If I add the cc: stable line in a patch and use git-send-email to post
the patch, git-send-email also posts the patch to the stable list -- is
this acceptable?
Totally acceptable.
Sometimes a patch may have to undergo multiple
revisions, meaning all the discussion emails go to the stable list
unnecessarily, and I guess this is not good?
It's not a problem at all, happens all the time and in fact I like it as
it gives us a heads-up that a patch is going to be eventually merged for
us to handle.
It looks like there is no git-send-email option to exclude an email.
No need to, don't worry about that at all.
thanks,
greg k-h