ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Greg KH <gregkh@linuxfoundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Sasha Levin <sashal@kernel.org>, ksummit@lists.linux.dev
Subject: Re: Proposal: Enhancing Commit Tagging for Stable Kernel Branches
Date: Mon, 15 Jul 2024 08:52:54 -0400	[thread overview]
Message-ID: <ef31a7c7546ef232665760aac98c8d7f20060bcc.camel@linux.ibm.com> (raw)
In-Reply-To: <3a357a63f67f3e6aff5e6d020d40b51fa24e0280.camel@linux.ibm.com>

On Mon, 2024-07-15 at 08:48 -0400, Mimi Zohar wrote:
> On Mon, 2024-07-15 at 10:02 +0200, Greg KH wrote:
> > 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.
> > 
> > But I doubt everyone wants to see that polute their mailing lists :(
> > 
> > Anyway, if people want to stick to the current, documented, process,
> > great, but as-is, trying to get people to follow that is rough and not
> > really working.
> 
> Sigh, I'm one of them, but I'd like to move to backporting "stable" only.
> Unfortunately, the more that you backport "Fixes:" the less likely maintainers
> (me) will remember to Cc stable.  Other than email, is there a way of letting
> you and Sasha know to only backport those with "Stable"?.  Instead of sending
> the email above to everyone, only send it maintainers who don't Cc stable
> properly/haven't notified you that they will.  The emails should get everyone
> else's attention. :)

Basically, reward good behavior, penalize bad behavior.

Mimi


  reply	other threads:[~2024-07-15 12:57 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-14 12:31 Sasha Levin
2024-07-14 13:35 ` James Bottomley
2024-07-14 15:35   ` Andrew Lunn
2024-07-14 16:34     ` James Bottomley
2024-07-14 18:38   ` Sasha Levin
2024-07-14 19:20     ` James Bottomley
2024-07-14 20:18       ` Sasha Levin
2024-07-15 18:00         ` Theodore Ts'o
2024-07-15 18:07           ` Mark Brown
2024-07-15 19:06           ` Dan Carpenter
2024-07-15 19:23             ` Steven Rostedt
2024-07-15 19:24             ` James Bottomley
2024-07-15 19:28               ` Steven Rostedt
2024-07-15 19:30                 ` James Bottomley
2024-07-15 19:39               ` Dan Carpenter
2024-07-16  6:30                 ` Greg KH
2024-07-15 20:25               ` Mauro Carvalho Chehab
2024-07-15 20:47             ` Dmitry Torokhov
2024-07-16  6:28               ` Greg KH
2024-07-16 12:20                 ` Takashi Iwai
2024-07-17 22:05                   ` Dan Carpenter
2024-07-18  7:34                     ` Takashi Iwai
2024-07-18 14:48                       ` Dan Carpenter
2024-07-18 14:56                         ` James Bottomley
2024-07-18 16:36                           ` Dan Carpenter
2024-07-19  0:49                             ` NeilBrown
2024-07-19  1:35                               ` Dan Carpenter
2024-07-19 11:55                                 ` Vegard Nossum
2024-07-23 14:14                                   ` Jiri Kosina
2024-07-16 14:51       ` Jason Gunthorpe
2024-07-16 19:38         ` Dan Carpenter
2024-07-15  6:15     ` Mauro Carvalho Chehab
2024-07-14 17:07 ` Linus Torvalds
2024-07-14 18:47   ` Sasha Levin
2024-07-14 19:27     ` Linus Torvalds
2024-07-14 20:27       ` Sasha Levin
2024-07-14 23:05         ` James Bottomley
2024-07-14 23:09           ` Linus Torvalds
2024-07-15  8:02             ` Greg KH
2024-07-15  8:53               ` Mauro Carvalho Chehab
2024-07-15 12:48               ` Mimi Zohar
2024-07-15 12:52                 ` Mimi Zohar [this message]
2024-07-15 14:34                   ` Alexandre Belloni
2024-07-15 14:40                     ` Greg KH
2024-07-15 15:00                       ` Jonathan Corbet
2024-07-15 15:07                         ` James Bottomley
2024-07-15 15:19                           ` Sasha Levin
2024-07-15 15:31                             ` James Bottomley
2024-07-15 15:42                             ` Dan Carpenter
2024-07-15 15:10                         ` Greg KH
2024-07-15 17:45                           ` Mauro Carvalho Chehab
2024-07-15 18:04                       ` Mark Brown
2024-07-15 20:51                         ` Dmitry Torokhov
2024-07-16  6:25                         ` Greg KH
2024-07-16 15:00                           ` Mark Brown
2024-07-14 23:29           ` NeilBrown
2024-07-14 23:29         ` Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ef31a7c7546ef232665760aac98c8d7f20060bcc.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox