Received-SPF: pass (google.com: domain of linux-kernel+bounces-148105-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Date: Wed, 17 Apr 2024 09:09:26 +0100
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: helpdesk@kernel.org, Greg KH <gregkh@linuxfoundation.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
Message-ID: <20240417090918.77360289@sal.lan>
In-Reply-To: <b452fd54-fdc6-47e4-8c26-6627f6b7eff3@leemhuis.info>
References: <b452fd54-fdc6-47e4-8c26-6627f6b7eff3@leemhuis.info>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Em Wed, 17 Apr 2024 09:48:18 +0200
Thorsten Leemhuis <linux@leemhuis.info> escreveu:

> 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.

Heh, a shorter name would make it a lot easier to remember, specially
since not wanting a patch to go to stable is an exception... I bet
I'll never remember the right syntax, needing to look at the docs
every time it would be used.

IMO, something like:
	no-stable
or
	nostable

would do the trick and would be a lot easier to remember.

Btw, IMO, it won't hurt accepting more than one variant that
could be allowed, e. g. using a regular expression like:

	(do)?[-_]?(nt|not?).*stable

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.

Just my 2 cents.

Regards,
Mauro