From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: linux-kernel@vger.kernel.org
Subject: Reporting Kernel Bugs
Date: Wed, 12 Oct 2011 14:08:38 -0400 [thread overview]
Message-ID: <4E95D7A6.6010603@canonical.com> (raw)
Hello,
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?
Thanks,
Joe
next reply other threads:[~2011-10-12 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 18:08 Joseph Salisbury [this message]
2011-10-12 18:13 ` Reporting Kernel Bugs Jiri Kosina
2011-10-12 18:17 ` Joseph Salisbury
2011-10-13 12:00 ` Joseph Salisbury
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=4E95D7A6.6010603@canonical.com \
--to=joseph.salisbury@canonical.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