workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	helpdesk@kernel.org,
	"workflows@vger.kernel.org" <workflows@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Please create the email alias do-not-apply-to-stable@kernel.org -> /dev/null
Date: Thu, 18 Apr 2024 09:04:53 +0200	[thread overview]
Message-ID: <d4853f43-2538-4a92-9ac4-aff5c7b0893e@leemhuis.info> (raw)
In-Reply-To: <2024041734-gleeful-freewill-b24b@gregkh>

On 17.04.24 15:38, Greg KH wrote:
> On Wed, Apr 17, 2024 at 03:21:12PM +0200, Thorsten Leemhuis wrote:
>> On 17.04.24 14:52, Konstantin Ryabitsev wrote:
>>> On Wed, Apr 17, 2024 at 09:48:18AM +0200, Thorsten Leemhuis wrote:
>>>> Could you please create the email alias
>>>> do-not-apply-to-stable@kernel.org which redirects all mail to /dev/null,
>>>> just like stable@kernel.org does?
>>>>
>>>> To quote:
>>>>
>>>>> How about:
>>>>> 	cc: <do-not-apply-to-stable@kernel.org> # Reason goes here, and must be present
>>>>>
>>>>> and we can make that address be routed to /dev/null just like
>>>>> <stable@kernel.org> is?
>>
>> FWIW, we could go back to what I initially proposed: use the existing
>> stable tag with a pre-defined comment to mark patches that AUTOSEL et.
>> al. should not pick up:
>> https://lore.kernel.org/all/c0a08b160b286e8c98549eedb37404c6e784cf8a.1712812895.git.linux@leemhuis.info/
> 
> If you can pick a better string, possibly, yes.

What did you think of Konstantin's

Cc: stable+noautosel@kernel.org # Reason

That looked like a good solution -- and I wondered why I did not come up
with that idea myself. Sure, "autosel" would also imply/mean "the
scripts/tools that look out for Fixes: tags", but does that matter?

> But in the end, your proposal seems to imply:
> 
> 	cc: stable@kernel.org	# Psych!  Just kidding, never backport this!
> 
> but really, that's just mean, and again, this is a VERY rare case you
> are trying to automate here. We have MUCH better and simpler ways for> maintainers to not have their subsystems scanned for stuff like this,
> why are we spending all of our time on this topic?

It started with various minor reasons -- and after some "this would be
nice to have" feedback it felt wrong to give up. It also looked like we
had some agreement already before a new discussion began.

Ciao, Thorsten

  parent reply	other threads:[~2024-04-18  7:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17  7:48 Thorsten Leemhuis
2024-04-17  7:55 ` Greg KH
2024-04-17  8:09 ` Mauro Carvalho Chehab
2024-04-17  8:16   ` Greg KH
2024-04-17  8:48     ` Willy Tarreau
2024-04-17 17:13       ` Florian Fainelli
2024-04-17 16:56     ` Mauro Carvalho Chehab
2024-04-17 12:52 ` Konstantin Ryabitsev
2024-04-17 13:15   ` Vlastimil Babka
2024-04-17 13:21   ` Thorsten Leemhuis
2024-04-17 13:25     ` Konstantin Ryabitsev
2024-04-17 13:38     ` Greg KH
2024-04-17 13:55       ` Konstantin Ryabitsev
2024-04-18  7:04       ` Thorsten Leemhuis [this message]
2024-04-18 13:20         ` Greg KH
2024-04-22 15:49           ` Thorsten Leemhuis
2024-04-22 19:25             ` Konstantin Ryabitsev
2024-04-22 21:46               ` Mauro Carvalho Chehab
2024-04-22 22:04                 ` Greg KH
2024-04-22 22:15                   ` Mauro Carvalho Chehab
2024-04-23  7:28                     ` Thorsten Leemhuis

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=d4853f43-2538-4a92-9ac4-aff5c7b0893e@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=gregkh@linuxfoundation.org \
    --cc=helpdesk@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=workflows@vger.kernel.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