Re: Proposal: Enhancing Commit Tagging for Stable Kernel Branches

[Mauro Carvalho Chehab <mchehab+huawei@kernel.org>]

Em Mon, 15 Jul 2024 10:02:54 +0200
Greg KH <gregkh@linuxfoundation.org> escreveu:

> On Sun, Jul 14, 2024 at 04:09:06PM -0700, Linus Torvalds wrote:
> > On Sun, 14 Jul 2024 at 16:06, James Bottomley
> > <James.Bottomley@hansenpartnership.com> wrote:  
> > >
> > > But we know how to enforce a unified view of process: we document it in
> > > Documentaion/process ...  
> > 
> > Hahhahhahaahh.
> > 
> > Ahh, you're such a kidder, James.  
> 
> Yeah, and that's the issue here, we have whole subsystems and many many
> maintainers and developers that do not follow this at all, hence our
> need to pull into stable commits that only have a "Fixes:" tag on it.
> 
> Now we can start running a bot on all submissions that says something
> like the one that I have been doing for the USB subsystem for the past
> few months, here's the text I use:
> 
> 	- You have marked a patch with a "Fixes:" tag for a commit that is in an
> 	  older released kernel, yet you do not have a cc: stable line in the
> 	  signed-off-by area at all, which means that the patch will not be
> 	  applied to any older kernel releases.  To properly fix this, please
> 	  follow the documented rules in the
> 	  Documentation/process/stable-kernel-rules.rst file for how to resolve
> 	  this.

Perhaps the text should also briefly describe how to make the bot ignore it
when there are good reasons for that. Something like:

	If the patch shall not be backported, please document it together
	with the rationale with:

	Cc: <stable+noautosel@kernel.org> # reason goes here, and must be present

> But I doubt everyone wants to see that polute their mailing lists :(

As people learn about that, the number of such emails will reduce.


Thanks,
Mauro