From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reporting Kernel Bugs
Date: Thu, 13 Oct 2011 08:00:34 -0400 [thread overview]
Message-ID: <4E96D2E2.8030208@canonical.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1110122011360.29079@twin.jikos.cz>
On 10/12/2011 02:13 PM, Jiri Kosina wrote:
> On Wed, 12 Oct 2011, Joseph Salisbury wrote:
>
>> Is there a way to report new kernel bugs while bugzilla.kernel.org is
>> down? I imagine many folks are now starting to have new reports stack
>> up.
>>
>> Also, is there an ETA on when bugzilla will be back available again?
>
> Just send an e-mail to appropriate mailinglist and CC
> responsible maintainer(s).
>
> That's what many people prefer to bugzilla anyway.
>
One additional question. Is there a way to work and search existing
bugs while bugzilla.kernel.org is unavailable?
next prev parent reply other threads:[~2011-10-13 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 18:08 Reporting Kernel Bugs Joseph Salisbury
2011-10-12 18:13 ` Jiri Kosina
2011-10-12 18:17 ` Joseph Salisbury
2011-10-13 12:00 ` Joseph Salisbury [this message]
2011-10-13 16:27 ` Jiri Kosina
2011-10-14 20:10 ` Jan Steinke
2011-10-14 20:23 ` David Rientjes
2011-10-15 12:01 ` Maciej Rutecki
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=4E96D2E2.8030208@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=jkosina@suse.cz \
--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