[CCing Sasha] On 18.04.24 15:20, Greg KH wrote: > On Thu, Apr 18, 2024 at 09:04:53AM +0200, Thorsten Leemhuis wrote: >> 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 >>>>>> >>>>>>> How about: >>>>>>> cc: # Reason goes here, and must be present >>>>>>> >>>>>>> and we can make that address be routed to /dev/null just like >>>>>>> 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 @Greg, BTW: should this be stable+noautosel@kernel.org or have a 'vger.' 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 >> 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? > > We can live with this, sure. In that case I guess I now also have to fix the scripts to honor that tag. @Greg: something like the attached for scripts/fixes_search perhaps? Was that the right one and are there any other scripts that might need something similar? @Sasha: are the scripts around autosel online somewhere? They need a similar change. Ciao, Thorsten