archive mirror
 help / color / mirror / Atom feed
From: "Artem S. Tashkinov" <>
To: Jani Nikula <>,
	Linux Kernel Mailing List <>,
Subject: Re: [PATCH v1 (RFC)] docs: discourage users from using
Date: Mon, 8 Nov 2021 13:17:45 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 11/8/21 13:00, Jani Nikula wrote:
> On Mon, 08 Nov 2021, "Artem S. Tashkinov" <> wrote:
>> It does *not* help one bit that we have different bug trackers and
>> mailing lists for a *single* component which is the kernel. No other
>> software project under the sun makes the user rack their head trying to
>> understand how and where to post bug reports.
> I suppose the kernel is a single component only from a fairly narrow
> user centric view. Sure, it would be nice, from a user perspective, to
> have a single bug tracker for everything. But behind the scenes, the
> kernel development community is so broad and fragmented it's basically
> impossible to get people to agree on a tracker that would suit everyone
> and that everyone would use. Furthermore, there are users that insist on
> reporting bugs on their own terms anyway, refusing to sign up to any
> trackers.
> Arguably "the single bug tracker" most users should report their kernel
> problems for triage first is their distro bug tracker.
>> Can we shut down completely? In its current form
>> it's nothing but disgrace.
> Works for me, ymmv.

Linux hackers probably don't need anything at all, I'm talking about
average people.

 From the Official Debian documentation ( ):

 > "If an oops is reproducible on latest please notify upstream via
email. Another way to notify upstream is to file a bug in".

Lots of bug reports about the kernel in the Debian bug tracker see this:

 > "Report upstream".

Which is the opposite of what you can see at

It's quite amazing that absolute most distros except maybe RedHat and
Ubuntu have zero people who can actually resolve kernel bugs yet the
kernel bugzilla denies the option of using it.

Anyways, looks like all the responsible people have their ears shut, so
let's leave everything as it is.

      reply	other threads:[~2021-11-08 13:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10 12:10 [PATCH v1 (RFC)] docs: discourage users from using Thorsten Leemhuis
2021-01-11 18:14 ` Randy Dunlap
2021-01-11 18:55   ` Thorsten Leemhuis
2021-01-11 23:42     ` Randy Dunlap
2021-01-12 17:34       ` Thorsten Leemhuis
2021-01-11 19:48 ` Konstantin Ryabitsev
2021-01-12 19:09   ` Thorsten Leemhuis
2021-01-13 11:17     ` Jani Nikula
2021-01-14 19:18       ` Konstantin Ryabitsev
2021-11-05 14:36 ` Artem S. Tashkinov
2021-11-05 14:42   ` Matthew Wilcox
2021-11-05 14:59     ` Artem S. Tashkinov
2021-11-08 11:43   ` Jani Nikula
2021-11-08 12:03     ` Artem S. Tashkinov
2021-11-08 13:00       ` Jani Nikula
2021-11-08 13:17         ` Artem S. Tashkinov [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).