From: "Artem S. Tashkinov" <aros@gmx.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Theodore Ts'o <tytso@mit.edu>,
Thorsten Leemhuis <linux@leemhuis.info>,
Greg KH <gregkh@linuxfoundation.org>,
workflows@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
ksummit@lists.linux.dev,
Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues"
Date: Sun, 2 Oct 2022 21:53:58 +0000 [thread overview]
Message-ID: <867b35b7-da2b-fed0-1f75-b2021d9be499@gmx.com> (raw)
In-Reply-To: <20221002213235.GA22532@1wt.eu>
On 10/2/22 21:32, Willy Tarreau wrote:
> On Sun, Oct 02, 2022 at 09:07:13PM +0000, Artem S. Tashkinov wrote:
>>>> Why are people are now blowing stuff out of proportion for no reason?
>>>
>>> Because the approach is wrong. As I explained it gives a false sense to
>>> the reporter that their issue is being handled while the simple fact that
>>> a message was sent to a person is in no way an engagement to do anything
>>> about it. LKML is a broadcast area. Everyone hopes someone else will
>>> respond and that eventually happens. When the reports are targetted, it
>>
>> No, it doesn't happen. Should I open LKML and send you a hundred of
>> unreplied emails over the past year alone?
>
> If that makes you feel better, feel free to do so. I'm not scared by
> only one hundred e-mails. What I'm impressed by, however, is that you're
> able to spot that many unreplied e-mails because I don't see as many. If
> you're that efficient at spotting them, maybe these are the ones you
> should just resend to make sure they're seen, and it would require less
> work (even on your side) than triaging issues.
So, we've been worked up about a _possible_ SPAM issue and your response
is ... create more SPAM? How does it solve all the other issues with
email I've identified?
>
>> Just before I GTFO I will leave this bug report here (already posted it
>> here but maybe I need to do it again and again):
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=204807
>>
>> Tell me honestly how ~255 comments, and a ton of collaboration over the
>> span of 2.5 years can be managed using email.
>
> What makes you think it would have taken that long over e-mail ? Between
> your first report and the first reply "this is not a bug", 18 months had
> elapsed already. The most active part of the discussion happened grouped
> on 3 days (2021-03-19 -> 22), where there were already some "I'm removing
> myself from the CC because the discussion isn't productive", then a large
> number of "me too" happened. Not sure how much useful this has been
> overall to the involved developers, given that it's impossible to stay
> focused on that long a thread and sum up all the information spanning
> over that many kernel versions and that many different hardware.
It's easy to join an existing bug report. Tell me how can I join an
existing email thread without being first subscribed to it? I certainly
can, absolute most people will not be able to.
What about sending large dump files? Should everyone on the mailing list
receive it?
A bug report is a simple plain list of messages in a single place which
could be read with a web browser. An email thread is anything but.
Searching through many emails at once? Good luck with that.
Replying to a particular email? Good luck with that.
It looks like you're under the impression that every Linux user who is
willing to ever use Linux must:
1) Subscribe to _all_ the existing mailing lists (just in case - what if
you need to work on something which was started by someone else)
2) Know the email etiquette
3) Learn to be persistent and resend (an unknown number of times) your
concerns hoping they will eventually be addressed.
Bugzilla: sign up once. Follow up. If you file a dupe, hopefully it will
be marked as a dupe. Everyone's happy. No particular skills, email
clients, formatting, referencing, etc. etc. etc.
All the developers busy and no one wants to work on your bug report?
That's Linux, you've got it for free. Submit a patch or pay someone
who'll fix your issue.
Regards,
Artem
>
> My gut feeling is that handling this over the ML would have resulted in:
> - a few "sorry, no solution, try to fix your BIOS"
> - "try this" => "it works, thank you".
> - "this fix above broke for me"
> - and a few such iterations until a satisfying enough solution would
> have been found. Maybe not in 2.5 years, maybe 6 months.
>
> But I could be wrong. I'm not claiming I know how people feel the most
> efficient. Just observing what we're seeing on the lists and what I'm
> used to dealing with in some bug trackers. If you want I can as well
> show you a bug I reported 19 years ago that's still in state "NEW",
> having seen little updates over the years. It had better been closed
> since then, TBH:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?format=multiple&id=11873
>
> Pretty close to your demo above except it lasted 8 times longer and
> has not seen progress by lack of interest. How's that different from
> what you complain about mailing lists ? Hmm ?
>
> Willy
next prev parent reply other threads:[~2022-10-02 21:54 UTC|newest]
Thread overview: 155+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aa876027-1038-3e4a-b16a-c144f674c0b0@leemhuis.info>
2022-09-29 11:33 ` Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues" Thorsten Leemhuis
2022-09-29 12:22 ` Artem S. Tashkinov
2022-09-29 12:52 ` Greg KH
2022-09-29 13:09 ` Artem S. Tashkinov
2022-09-29 13:21 ` Greg KH
2022-09-29 13:23 ` Konstantin Ryabitsev
2022-09-29 13:04 ` Konstantin Ryabitsev
2022-09-29 13:31 ` Artem S. Tashkinov
2022-09-29 13:43 ` Greg KH
2022-09-29 13:53 ` Konstantin Ryabitsev
2022-09-29 14:22 ` Artem S. Tashkinov
2022-09-29 14:54 ` Slade Watkins
2022-09-29 16:42 ` Laurent Pinchart
2022-09-29 19:00 ` Slade Watkins
2022-09-30 9:35 ` Thorsten Leemhuis
2022-09-30 13:23 ` Laurent Pinchart
2022-09-30 16:19 ` Bird, Tim
2022-09-30 16:34 ` Artem S. Tashkinov
2022-09-30 16:47 ` Laurent Pinchart
2022-10-01 1:18 ` Theodore Ts'o
2022-10-01 2:47 ` Slade Watkins
2022-10-01 7:57 ` Bagas Sanjaya
2022-10-01 13:01 ` Theodore Ts'o
2022-10-03 6:55 ` Christoph Hellwig
2022-09-30 17:36 ` Slade Watkins
2022-09-30 16:36 ` Laurent Pinchart
2022-09-30 17:28 ` Luck, Tony
2022-09-30 17:49 ` Slade Watkins
2022-09-30 20:04 ` Randy Dunlap
2022-09-30 20:29 ` Thorsten Leemhuis
2022-09-29 15:31 ` Konstantin Ryabitsev
2022-09-29 15:39 ` Slade Watkins
2022-09-29 16:06 ` Artem S. Tashkinov
2022-09-29 20:26 ` Slade Watkins
2022-09-30 8:47 ` Thorsten Leemhuis
2022-09-30 9:03 ` Artem S. Tashkinov
2022-09-30 10:37 ` Slade Watkins
2022-09-30 15:32 ` Laurent Pinchart
2022-10-03 11:44 ` Jani Nikula
2022-09-29 15:26 ` James Bottomley
2022-09-30 8:52 ` Artem S. Tashkinov
2022-09-29 13:47 ` Steven Rostedt
2022-09-29 14:02 ` Thorsten Leemhuis
2022-09-29 14:12 ` Steven Rostedt
2022-10-01 10:30 ` Artem S. Tashkinov
2022-10-01 10:39 ` Greg KH
2022-10-01 10:47 ` Artem S. Tashkinov
2022-10-01 10:57 ` Thorsten Leemhuis
2022-10-01 11:21 ` Artem S. Tashkinov
2022-10-01 11:34 ` Thorsten Leemhuis
2022-10-01 13:07 ` Theodore Ts'o
2022-10-01 14:58 ` Artem S. Tashkinov
2022-10-02 12:18 ` Theodore Ts'o
2022-10-02 12:49 ` Artem S. Tashkinov
2022-10-02 14:35 ` Greg KH
2022-10-02 19:27 ` Artem S. Tashkinov
2022-10-02 20:46 ` Linus Torvalds
2022-10-02 20:56 ` Artem S. Tashkinov
2022-10-02 21:07 ` Linus Torvalds
2022-10-02 21:27 ` Artem S. Tashkinov
2022-10-02 21:40 ` Willy Tarreau
2022-10-02 21:57 ` Artem S. Tashkinov
2022-10-02 14:48 ` Slade Watkins
2022-10-02 19:37 ` Artem S. Tashkinov
2022-10-02 21:11 ` Laurent Pinchart
2022-10-02 21:38 ` Artem S. Tashkinov
2022-10-02 15:05 ` Konstantin Ryabitsev
2022-10-02 19:43 ` Artem S. Tashkinov
2022-10-02 20:54 ` Willy Tarreau
2022-10-02 21:07 ` Artem S. Tashkinov
2022-10-02 21:32 ` Willy Tarreau
2022-10-02 21:53 ` Artem S. Tashkinov [this message]
2022-10-03 6:37 ` Geert Uytterhoeven
2022-10-03 7:49 ` Artem S. Tashkinov
2022-10-03 10:04 ` Willy Tarreau
2022-10-02 15:56 ` Al Viro
2022-10-02 17:22 ` Slade Watkins
2022-10-02 16:08 ` Geert Uytterhoeven
2022-10-02 16:10 ` Geert Uytterhoeven
2022-10-02 16:32 ` Joe Perches
2022-10-02 18:56 ` Joe Perches
2022-10-02 19:46 ` Artem S. Tashkinov
2022-10-02 17:57 ` Willy Tarreau
2022-10-02 19:55 ` Artem S. Tashkinov
2022-10-02 20:40 ` Willy Tarreau
2022-10-02 18:13 ` Steven Rostedt
2022-10-02 20:14 ` Artem S. Tashkinov
2022-10-02 22:08 ` Steven Rostedt
2022-10-02 22:20 ` Artem S. Tashkinov
2022-10-02 22:28 ` Steven Rostedt
2022-10-02 23:04 ` Al Viro
2022-10-02 23:21 ` Steven Rostedt
2022-10-03 7:41 ` Artem S. Tashkinov
2022-10-03 8:55 ` Mike Rapoport
2022-10-03 9:15 ` David Laight
2022-10-03 9:16 ` Artem S. Tashkinov
2022-10-03 9:26 ` Geert Uytterhoeven
2022-10-03 9:40 ` Artem S. Tashkinov
2022-10-03 10:26 ` Mike Rapoport
2022-10-03 14:20 ` Steven Rostedt
2022-10-03 18:24 ` Al Viro
2022-10-03 19:07 ` Steven Rostedt
2022-10-03 20:28 ` Slade Watkins
2022-10-04 12:16 ` Artem S. Tashkinov
2022-10-04 12:32 ` Geert Uytterhoeven
2022-10-04 22:45 ` Steven Rostedt
2022-10-03 14:22 ` Konstantin Ryabitsev
2022-10-04 12:21 ` Artem S. Tashkinov
2022-10-04 14:20 ` Konstantin Ryabitsev
2022-10-03 15:37 ` Konstantin Ryabitsev
2022-10-04 7:37 ` Thorsten Leemhuis
2022-10-04 7:56 ` Conor Dooley
2022-10-04 12:24 ` Artem S. Tashkinov
2022-10-04 14:48 ` Konstantin Ryabitsev
2022-10-02 20:41 ` Slade Watkins
2022-10-02 20:52 ` Slade Watkins
2022-10-02 21:06 ` Laurent Pinchart
2022-10-02 22:18 ` Steven Rostedt
2022-10-02 22:41 ` Laurent Pinchart
2022-10-02 23:59 ` Slade Watkins
2022-10-02 18:17 ` Geert Uytterhoeven
2022-10-02 20:17 ` Artem S. Tashkinov
2022-10-02 20:48 ` Willy Tarreau
2022-10-02 19:59 ` Laurent Pinchart
2022-10-02 20:19 ` Artem S. Tashkinov
2022-10-02 20:26 ` Laurent Pinchart
2022-10-02 13:25 ` Slade Watkins
2022-10-02 9:03 ` Geert Uytterhoeven
2022-10-02 9:06 ` Artem S. Tashkinov
2022-10-02 9:25 ` Geert Uytterhoeven
2022-10-02 7:37 ` Takashi Iwai
2022-10-02 8:23 ` Artem S. Tashkinov
2022-10-02 8:53 ` Geert Uytterhoeven
2022-10-02 9:14 ` Takashi Iwai
2022-10-03 10:10 ` Thorsten Leemhuis
2022-10-03 11:18 ` Slade Watkins
2022-10-03 12:59 ` Thorsten Leemhuis
2022-10-03 15:26 ` Steven Rostedt
2022-10-03 15:44 ` Laurent Pinchart
2022-10-03 15:51 ` Steven Rostedt
2022-10-03 15:59 ` Laurent Pinchart
2022-10-03 16:03 ` Steven Rostedt
2022-10-04 8:41 ` Thorsten Leemhuis
2022-10-04 9:20 ` Geert Uytterhoeven
2022-10-04 10:16 ` Thorsten Leemhuis
2022-10-04 10:45 ` Geert Uytterhoeven
[not found] ` <20221004175354.bfvg3vhfqch35ib5@meerkat.local>
[not found] ` <Yzx1T05Ut0of55KY@kroah.com>
2022-10-04 18:13 ` Konstantin Ryabitsev
[not found] ` <87fsg3s8co.fsf@intel.com>
2022-10-04 19:24 ` Konstantin Ryabitsev
[not found] ` <c74d9d75-4428-e22d-1adb-334b1173d871@leemhuis.info>
2022-10-04 20:25 ` Konstantin Ryabitsev
2022-10-05 9:00 ` Thorsten Leemhuis
2022-10-05 9:57 ` Hans de Goede
2022-10-12 16:12 ` Thorsten Leemhuis
2022-10-17 13:57 ` Thorsten Leemhuis
2022-10-17 20:47 ` Konstantin Ryabitsev
2022-10-18 16:24 ` Rafael J. Wysocki
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=867b35b7-da2b-fed0-1f75-b2021d9be499@gmx.com \
--to=aros@gmx.com \
--cc=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mario.limonciello@amd.com \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=w@1wt.eu \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).