From: Thorsten Leemhuis <linux@leemhuis.info>
To: helpdesk@kernel.org
Cc: Greg KH <gregkh@linuxfoundation.org>,
"workflows@vger.kernel.org" <workflows@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Please create the email alias do-not-apply-to-stable@kernel.org -> /dev/null
Date: Wed, 17 Apr 2024 09:48:18 +0200 [thread overview]
Message-ID: <b452fd54-fdc6-47e4-8c26-6627f6b7eff3@leemhuis.info> (raw)
Hi kernel.org helpdesk!
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?
That's an idea GregKH brought up a few days ago here:
https://lore.kernel.org/all/2024041123-earthling-primarily-4656@gregkh/
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?
There was some discussion about using something shorter, but in the end
there was no strong opposition and the thread ended a a few days ago.
The goal is to have a tag that developers can use in Linux kenrel
commits that have a Fixes: tag, but nevertheless should not be
backported by the stable-team without explicit request. The thread
linked above explains this in more detail. Once the address exists I'll
resubmit the patches in question that will document the tag.
Is asking for this here like this the right way? If I need to file a
ticket somewhere or some ack from a higher authority, just let me know!
Ciao, Thorsten
next reply other threads:[~2024-04-17 7:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 7:48 Thorsten Leemhuis [this message]
2024-04-17 7:55 ` Please create the email alias do-not-apply-to-stable@kernel.org -> /dev/null 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
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=b452fd54-fdc6-47e4-8c26-6627f6b7eff3@leemhuis.info \
--to=linux@leemhuis.info \
--cc=gregkh@linuxfoundation.org \
--cc=helpdesk@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).