From: Willy Tarreau <w@1wt.eu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Thorsten Leemhuis <linux@leemhuis.info>,
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: Wed, 17 Apr 2024 10:48:56 +0200 [thread overview]
Message-ID: <Zh+M+NWKbpQeT/Z6@1wt.eu> (raw)
In-Reply-To: <2024041715-calorie-late-c4de@gregkh>
On Wed, Apr 17, 2024 at 10:16:26AM +0200, Greg KH wrote:
> > at the scripts used by stable developers - and maybe at the ML server - to
> > catch different variations won't hurt, as it sounds likely that people will
> > end messing up with a big name like "do-not-apply-to-stable", typing
> > instead things like:
> >
> > do_not_apply_to_stable
> > dont-apply-to-stable
> >
> > and other variants.
>
> I want this very explicit that someone does not want this applied, and
> that it has a reason to do so. And if getting the email right to do so
> is the issue with that, that's fine. This is a very rare case that
> almost no one should normally hit.
For using a comparable approach in haproxy on a daily basis, I do see
the value in this. We just mark a lot of fixes "no backport needed" or
"no backport needed unless blablabla" for everything that is only
relevant to the dev tree, and that's a huge time saver for those working
on the backports later.
Maybe "not-for-stable" would be both shorter and easier to remember BTW ?
Regards,
Willy
next prev parent reply other threads:[~2024-04-17 8:49 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 [this message]
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=Zh+M+NWKbpQeT/Z6@1wt.eu \
--to=w@1wt.eu \
--cc=gregkh@linuxfoundation.org \
--cc=helpdesk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mchehab@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