From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Theodore Tso <tytso@mit.edu>,
Robert Bradbury <robert.bradbury@gmail.com>
Cc: Thomas Backlund <tmb@mandriva.org>,
LKML <linux-kernel@vger.kernel.org>,
Frans Pop <elendil@planet.nl>
Subject: Re: RFC: Updating the LKML bug reporting/updating framework
Date: Mon, 26 Oct 2009 19:40:45 +0100 [thread overview]
Message-ID: <4AE5ED2D.2010708@s5r6.in-berlin.de> (raw)
In-Reply-To: <20091026145637.GE13941@mit.edu>
Theodore Tso wrote:
> Most end users who use a Linux distribution will have a much better
> time if they use the support channels (bugzilla, irc, web forums,
> etc.) for their particular Linux distribution.
[...]
> even some community distributions, such as
> Ubuntu, do add a significant number of "value add" (and thus, bugs :-)
> to their kernels.
The downside is that such bugtrackers appear to be chronically
understaffed in the triage department. Therefore, bugs which could look
like potential upstream bugs to a somewhat trained eye are far too
rarely reported to upstream by distro bug triage teams.
> There are also individual sublists for people who are only working on
> a specific part of the kernel (i.e., the linux-ext4 mailing list, the
> linux-scsi mailing list, etc).
Robert,
these mailing lists can be found in the MAINTAINERS file in the root of
the kernel sources. The reporting-bugs page which Thomas mentioned
points to this file as a source for contact persons, but the list
addresses in there are IMO even more important.
About bugzilla.kernel.org: It's more a tracker than a reporting tool.
--
Stefan Richter
-=====-==--= =-=- ==-=-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2009-10-26 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 22:59 RFC: Updating the LKML bug reporting/updating framework Robert Bradbury
2009-10-25 23:32 ` Thomas Backlund
2009-10-26 12:12 ` Robert Bradbury
2009-10-26 13:12 ` Frans Pop
2009-10-26 14:56 ` Theodore Tso
2009-10-26 18:40 ` Stefan Richter [this message]
2009-10-27 6:44 ` Pavel Machek
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=4AE5ED2D.2010708@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.bradbury@gmail.com \
--cc=tmb@mandriva.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.