From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Bruno Prémont" <bonbons@linux-vserver.org>, carla.sella@gmail.com
Cc: linux-kernel@vger.kernel.org, Maciej Rutecki <maciej.rutecki@gmail.com>
Subject: Re: reporting a bug
Date: Wed, 26 Oct 2011 22:15:07 +0200 [thread overview]
Message-ID: <20111026221507.13f705ee@stein> (raw)
In-Reply-To: <20111026215109.24e0e737@neptune.home>
On Oct 26 Bruno Prémont wrote:
> On Wed, 26 October 2011 Carla Sella <carla.sella@gmail.com> wrote:
> > Hello, My name is Carla and I'm member of the Ubuntu laptop testing team.
> > I was asked to report a bug upstream on bugzilla.kernel.org.
> > As bugzilla.kernel.org is down, must I wait for it to be restored or is
> > there an alternative way to report a bug ?
> > Thank you.
>
> The alternative is to report the bug here, CCing the appropriate
> subsystem lists (and later filing the bug under bugzilla once it comes
> back - if needed)
Even when bugzilla.kernel.org was functional, the better way to report
kernel bugs was widely regarded to post at LKML (and any appropriate
subsystem mailinglist). Many (?) developers consider bugzilla.kernel.org
to be a _tracking_ tool rather than a reporting tool. Some developers did
not like to interact with bugzilla.kernel.org at all.
I too think that bug reporting and bug tracking are not entirely the same,
and that LKML (or kernel subsystem mailinglists, respectively) are
usually preferable for bug reporting.
--
Stefan Richter
-=====-==-== =-=- ==-=-
http://arcgraph.de/sr/
prev parent reply other threads:[~2011-10-26 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 19:48 reporting a bug Carla Sella
2011-10-26 19:51 ` Bruno Prémont
2011-10-26 20:00 ` Maciej Rutecki
2011-10-26 20:15 ` Stefan Richter [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:
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=20111026221507.13f705ee@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=bonbons@linux-vserver.org \
--cc=carla.sella@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
/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