From: Thorsten Leemhuis <linux@leemhuis.info>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ksummit <ksummit-discuss@lists.linuxfoundation.org>,
workflows@vger.kernel.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions
Date: Mon, 22 Mar 2021 20:25:15 +0100 [thread overview]
Message-ID: <62b60247-7838-a624-706e-b1a54785b2a5@leemhuis.info> (raw)
In-Reply-To: <CAHk-=wgiYqqLzsb9-UpfH+=ktk7ra-2fOsdc_ZJ7WF47wS73CA@mail.gmail.com>
On 22.03.21 19:32, Linus Torvalds wrote:
> On Mon, Mar 22, 2021 at 8:18 AM Thorsten Leemhuis <linux@leemhuis.info> wrote:
>>
>> I even requested a
>> "linux-regressions@vger.kernel.org" a while later, but didn't hear
>> anything back; and, sadly, about the same time I started having trouble
>> finding spare time for working on regression tracking. :-/
>
> Honestly, I'd much prefer the name 'linux-regressions' as being much
> more targeted than 'linux-issues'.
That only solves one of the two problem I'm trying to solve (albeit the
one that is more important to me). That way users still have no easy way
to query for reports about issues that are no regressions – say
something is broken and they have no idea if it once worked or never
worked at all.
> Make it clear that the list is only
> for regressions that people can describe some way, rather than some
> general "I have issues with xyz".
>
> The more clear-cut the list is, the better, I think.
I agree to the last point and yeah, maybe regressions are the more
important problem we should work on – at least from the perspective of
kernel development. But from the users perspective (and
reporting-issues.rst is written for that perspective) it feel a bit
unsatisfying to not have a solution to query for existing report,
regressions or not. Hmmmm...
Ciao, Thorsten
next prev parent reply other threads:[~2021-03-22 19:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 15:18 RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions Thorsten Leemhuis
2021-03-22 16:55 ` [Ksummit-discuss] " Lukas Bulwahn
2021-03-22 19:49 ` Thorsten Leemhuis
2021-03-22 17:16 ` Konstantin Ryabitsev
2021-03-22 17:57 ` [Ksummit-discuss] " James Bottomley
2021-03-22 18:34 ` Eric Wong
2021-03-22 18:55 ` Thorsten Leemhuis
2021-03-22 19:20 ` Konstantin Ryabitsev
2021-03-22 18:32 ` Linus Torvalds
2021-03-22 19:25 ` Thorsten Leemhuis [this message]
2021-03-22 21:56 ` [Ksummit-discuss] " Theodore Ts'o
2021-03-23 8:57 ` Thorsten Leemhuis
2021-03-23 15:01 ` Konstantin Ryabitsev
2021-03-23 19:09 ` Thorsten Leemhuis
2021-03-23 18:11 ` Theodore Ts'o
2021-03-23 18:51 ` Thorsten Leemhuis
2021-03-23 14:57 ` Luis Chamberlain
2021-03-23 16:20 ` Steven Rostedt
2021-03-23 16:30 ` [Ksummit-discuss] " James Bottomley
2021-03-23 21:43 ` Konstantin Ryabitsev
2021-03-23 23:11 ` Eric Wong
2021-03-23 18:07 ` Theodore Ts'o
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=62b60247-7838-a624-706e-b1a54785b2a5@leemhuis.info \
--to=linux@leemhuis.info \
--cc=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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).