From: Greg KH <gregkh@linuxfoundation.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Jonathan Corbet <corbet@lwn.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v1 1/2] MAINTAINERS: add regressions mailing list
Date: Wed, 7 Apr 2021 16:56:43 +0200 [thread overview]
Message-ID: <YG3IK46M4LNWp3EO@kroah.com> (raw)
In-Reply-To: <3121a1cd-47c6-b26e-0cb3-71872d5ffc65@leemhuis.info>
On Wed, Apr 07, 2021 at 12:51:43PM +0200, Thorsten Leemhuis wrote:
> On 07.04.21 11:56, Greg KH wrote:
> > On Wed, Apr 07, 2021 at 11:21:55AM +0200, Thorsten Leemhuis wrote:
> >> Add the newly created regression mailing list finally created after it
> >> already had been agreed on during the maintainers summit 2017 (see
> >> https://lwn.net/Articles/738216/ ). The topic was recently discussed
> >> again, where an idea to create a broader list for all issues was
> >> discussed, but Linus preferred a more targeted list:
> >> https://lkml.kernel.org/r/CAHk-=wgiYqqLzsb9-UpfH+=ktk7ra-2fOsdc_ZJ7WF47wS73CA@mail.gmail.com/
> >>
> >> Hence, the creation for that list was asked for and granted:
> >> https://bugzilla.kernel.org/show_bug.cgi?id=212557
> >>
> >> In the end it became regressions@lists.linux.dev instead of
> >> linux-regressions@lists.linux.dev as 'Linux' is redundant in the latter
> >> case.
> >>
> >> Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
> >> ---
> >> I was a bit unsure how to add that list to MAINTAINERS. I considered
> >> adding a 'M:' with my name and email address there as well, but getting
> >> CCed on a lot of regression reports might be a bit much. I also left a
> >> 'S: supported' out, as that doesn't make much sense in this case afaics;
> >> and I checked, there are other entries that don't have those two (but
> >> it's rare).
> >
> > Put your name there, you are the "maintainer of regressions!" :)
>
> Okay, will do. :-D
>
> /me wonders why he suddenly feels like entering a self-made trap ;-)
>
> > [...]
> >> +REGRESSIONS
> >> +L: regressions@lists.linux.dev
> >> +K: regression
> >
> > A bit more information here perhaps? This will not really help anyone
> > out to know what to do.
>
> Did you mean a different headline for the entry? Or would you suggest
> to use a webpage (W:) for that or a Subsystem Profile document (P:)
> here? Using either of the two latter was the plan, but for now I'm a bit
> unsure what to write there except maybe "Thorsten is working on a
> semi-automatic solution for tracking Linux kernel regressions. Details
> will follow. For now report regressions as outlined in
> reporting-issues.rst; but in case you have any problem or think there is
> a regressions not handled appropriately by the maintainers, get him
> involved, he'll try to help".
>
> Or did you have something totally different in mind?
Well, "K: regression" is not a regex, so that's not going to
really help much.
How about something simple like:
KERNEL REGRESSIONS:
M: Thorsten Leemhuis <linux@leemhuis.info>
L: regressions@lists.linux.dev
S: Supported
That looks a bit more like other entries, has a name and a list and a
state of your status for this work.
Would that work?
thanks,
greg k-h
next prev parent reply other threads:[~2021-04-07 14:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 9:21 [RFC PATCH v1 0/2] Add regression mailing list with basics for tracking Thorsten Leemhuis
2021-04-07 9:21 ` [RFC PATCH v1 1/2] MAINTAINERS: add regressions mailing list Thorsten Leemhuis
2021-04-07 9:56 ` Greg KH
2021-04-07 10:51 ` Thorsten Leemhuis
2021-04-07 14:56 ` Greg KH [this message]
2021-04-07 17:53 ` Thorsten Leemhuis
2021-04-07 9:21 ` [RFC PATCH v1 2/2] docs: reporting-issues: make everyone CC the regressions list Thorsten Leemhuis
2021-04-07 10:00 ` Greg KH
2021-04-07 11:21 ` Thorsten Leemhuis
2021-04-07 14:58 ` Greg KH
2021-04-08 17:31 ` Jonathan Corbet
2021-04-09 11:54 ` 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=YG3IK46M4LNWp3EO@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).