workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Greg KH <gregkh@linuxfoundation.org>, Sasha Levin <sashal@kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.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 17:49:29 +0200	[thread overview]
Message-ID: <655ce2a3-eb04-4ade-999e-23fc5dc5fb3a@leemhuis.info> (raw)
In-Reply-To: <2024041830-karaoke-aspirate-df00@gregkh>

[-- Attachment #1: Type: text/plain, Size: 1979 bytes --]

[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: <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?
>>>>
>>>> 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

[-- Attachment #2: 0001-scripts-fixes_search-honor-noautosel-tag.patch --]
[-- Type: text/x-patch, Size: 1326 bytes --]

From 1e973a069b07f8c045401a7d3d20ea760a27422f Mon Sep 17 00:00:00 2001
From: Thorsten Leemhuis <linux@leemhuis.info>
Date: Mon, 22 Apr 2024 17:31:01 +0200
Subject: [PATCH] scripts/fixes_search: honor noautosel tag

Ignore commits that contain a soon to be documented tag that is
meant to exclude commits from processing by scripts like
scripts/fixes_search.

Link: https://lore.kernel.org/all/2024041830-karaoke-aspirate-df00@gregkh/ [1]
Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
---
 scripts/fixes_search | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/scripts/fixes_search b/scripts/fixes_search
index aaa12ec..950509f 100755
--- a/scripts/fixes_search
+++ b/scripts/fixes_search
@@ -131,6 +131,13 @@ for commit in $(git rev-list --reverse --no-merges "${git_range}"); do
 	# logn "commit = ${txtgrn}${commit}${txtrst}	"
 	logn "${txtgrn}${commit}${txtrst}	"
 
+	# Check if we are supposed to ignore the commit
+	no_autosel=$(git log -1 --format='%B' "HEAD" | grep -i '^[[:space:]]*[Cc][Cc]:[[:space:]]*<stable+noautosel@')
+	if [ "${no_autosel}" ] ; then
+		log "${txtblu}contains noautosel tag${txtrst}"
+		continue
+	fi
+
 	# Try to find "Fixes" tag in commit
 	fixes_lines=$(git log -1 --format='%B' "${commit}" | grep -i '^[[:space:]]*Fixes:')
 	if [ "${fixes_lines}" == "" ] ; then
-- 
2.44.0


  reply	other threads:[~2024-04-22 15: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
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 [this message]
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=655ce2a3-eb04-4ade-999e-23fc5dc5fb3a@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=gregkh@linuxfoundation.org \
    --cc=helpdesk@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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