From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Thorsten Leemhuis <linux@leemhuis.info>,
Greg KH <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.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: Mon, 22 Apr 2024 22:46:37 +0100 [thread overview]
Message-ID: <20240422224637.01bb3058@sal.lan> (raw)
In-Reply-To: <20240422-stoic-sawfly-of-protection-db8bfe@lemur>
Em Mon, 22 Apr 2024 15:25:18 -0400
Konstantin Ryabitsev <konstantin@linuxfoundation.org> escreveu:
> On Mon, Apr 22, 2024 at 05:49:29PM +0200, Thorsten Leemhuis wrote:
> > @Greg, BTW: should this be stable+noautosel@kernel.org or have a
> > 'vger.'
>
> No vger, just stable+whatever@kernel.org.
>
> > in it, e.g. stable+noautosel@vger.kernel.org? I assume without 'vger.'
> > is fine, just wanted to be sure, as
> > Documentation/process/stable-kernel-rules.rst in all other cases
> > specifies stable@vger.kernel.org, so people are likely to get confused.
> > :-/ #sigh
>
> These serve two different purposes:
>
> stable@kernel.org (goes into devnull)
> stable@vger.kernel.org (actual mailing list)
>
> Confusion happens all the time, unfortunately.
Yeah, I did already used stable@kernel.org a few times in the
past.
IMO, the best would be either for stable to also accept it or for
kernel.org mail server to return an error message (only to the
submitter) warning about the invalid address, eventually with a
hint message pointing to the correct value.
>
> Notably, even if someone uses stable+noautosel@vger.kernel.org, it won't
> do anything terrible (it won't bounce, it'll just quietly go into
> nowhere because that's not a valid expansion command).
>
> -K
>
next prev parent reply other threads:[~2024-04-22 21:46 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
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 [this message]
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=20240422224637.01bb3058@sal.lan \
--to=mchehab@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=helpdesk@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=sashal@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