From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Lars Noodén" <lars.nooden@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: where to report bugs while bugzilla.kernel.org is down?
Date: Tue, 1 Nov 2011 18:19:20 +0100 [thread overview]
Message-ID: <20111101181920.2c6655dd@stein> (raw)
In-Reply-To: <4EB0205E.4050602@gmail.com>
On Nov 01 Lars Noodén wrote:
> bugzilla.kernel.org has been down for a while and it may be a while
> before it is up again. In the mean time how should bugs be reported?
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881593
Bugs should be reported on LKML and/or if applicable on a respective
subsystem mailinglist. (See MAINTAINERS file of the kernel source.)
Even when bugzilla.kernel.org comes back, report bugs preferably to
mailinglists. Bugzilla is a bug tracker, not so much a reporting tool.
Some maintainers and the good people who track kernel regressions make use
of bugzilla.kernel.org to keep record of bugs. Furthermore, it can of
course be used by reporters too especially if they need to upload
screenshots of a kernel panic or large log files etc..
(That said, bug reports which are entered into bugzilla instead of posted
to a mailinglist are usually forwarded to people or mailinglists who might
be able to handle them.)
--
Stefan Richter
-=====-==-== =-== ----=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2011-11-01 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 16:37 where to report bugs while bugzilla.kernel.org is down? Lars Noodén
2011-11-01 17:19 ` Stefan Richter [this message]
2012-01-02 14:24 ` Vlado Plaga
[not found] <hSpxx-3yk-23@gated-at.bofh.it>
[not found] ` <hSqad-4I9-3@gated-at.bofh.it>
[not found] ` <ieUkW-2mt-5@gated-at.bofh.it>
2012-01-02 19:32 ` D. Stussy
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=20111101181920.2c6655dd@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=lars.nooden@gmail.com \
--cc=linux-kernel@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