From: Matthias Brugger <mbrugger@suse.com>
To: Thorsten Leemhuis <linux@leemhuis.info>,
linux-doc@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: workflows@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [RFC PATCH v2 1/2] docs: add a document about regression handling
Date: Fri, 7 Jan 2022 18:44:40 +0100 [thread overview]
Message-ID: <8e6f07ef-10fe-381c-3a8d-db497492036c@suse.com> (raw)
In-Reply-To: <1126ce91-f22b-c397-4d1e-13d290a424a5@leemhuis.info>
On 07/01/2022 17:51, Thorsten Leemhuis wrote:
> On 07.01.22 16:37, Matthias Brugger wrote:
>> On 07/01/2022 15:21, Thorsten Leemhuis wrote:
>>> Create a document explaining various aspects around regression handling
>>> and tracking both for users and developers. Among others describe the
>>> first rule of Linux kernel development and what it means in practice.
>>> Also explain what a regression actually is and how to report one
>>> properly. The text additionally provides a brief introduction to the bot
>>> the kernel's regression tracker uses to facilitate his work. To sum
>>> things up, provide a few quotes from Linus to show how serious he takes
>>> regressions.
>>>
>>> Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
>> [...]
>>> +The important bits for people fixing regressions
>>> +================================================
>>> +
>>> +When receiving regression reports by mail, check if the reporter CCed
>>> `the
>>> +regression mailing list <https://lore.kernel.org/regressions/>`_
>>> +(regressions@lists.linux.dev). If not, forward or bounce the report
>>> to the Linux
>>> +kernel's regression tracker (regressions@leemhuis.info), unless you
>>> plan on
>>
>> I would have expected it to be the same mailing list
>> (regressions@lists.linux.dev), is this a typo maybe?
>
> Thx for taking a look. Hmm. That's possible, but I (and the grep call I
> just ran) fail to spot the typo.
>
> Maybe the wording is to confusing: regressions@lists.linux.dev is the
> list, regressions@leemhuis.info is a dedicated email address I (the
> kernel's regression tracker) use for regression tracking (which reminds
> me: maybe I should ask for a alias like regressions@kernel.org or
> regression-tracker@kernel.org).
Yes it's the wording then :)
Anyway I just wonder why you we should send the regression to the regressions
email list, but only to the tracker email address. For me that's the confusing
part. I'd expect to send it to the list as well and the tracker takes it from
there. If for any reason someone does not want to send a regression to the list,
then he can send it to the tracker directly. That's my understanding of how this
works. If that's correct then I'd say we should just explain the difference.
Regards,
Matthias
>
> Ciao, Thorsten
>
next prev parent reply other threads:[~2022-01-07 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 14:21 [RFC PATCH v2 0/2] docs: add a text about regressions to the Linux kernel's documentation Thorsten Leemhuis
2022-01-07 14:21 ` [RFC PATCH v2 1/2] docs: add a document about regression handling Thorsten Leemhuis
2022-01-07 15:37 ` Matthias Brugger
2022-01-07 16:51 ` Thorsten Leemhuis
2022-01-07 17:44 ` Matthias Brugger [this message]
2022-01-10 11:40 ` Thorsten Leemhuis
2022-01-10 12:13 ` Matthias Brugger (SUSE)
2022-01-07 14:21 ` [RFC PATCH v2 2/2] docs: regressions.rst: rules of thumb for handling regressions Thorsten Leemhuis
2022-01-07 16:28 ` [RFC PATCH v2 0/2] docs: add a text about regressions to the Linux kernel's documentation Greg Kroah-Hartman
2022-01-07 16:41 ` Thorsten Leemhuis
2022-01-07 16:42 ` 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=8e6f07ef-10fe-381c-3a8d-db497492036c@suse.com \
--to=mbrugger@suse.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lukas.bulwahn@gmail.com \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).