From: Jan Steinke <jan.steinke@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Reporting Kernel Bugs
Date: Fri, 14 Oct 2011 20:10:36 +0000 (UTC) [thread overview]
Message-ID: <loom.20111014T220901-636@post.gmane.org> (raw)
In-Reply-To: <alpine.LRH.2.00.1110122011360.29079@twin.jikos.cz>
Jiri Kosina <jkosina <at> suse.cz> writes:
> Just send an e-mail to appropriate mailinglist and CC
> responsible maintainer(s).
>
> That's what many people prefer to bugzilla anyway.
>
How do I know the responsible maintainer(s)? How do I know if the bug is
confirmed or accepted?
next prev parent reply other threads:[~2011-10-14 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 18:08 Joseph Salisbury
2011-10-12 18:13 ` 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 [this message]
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=loom.20111014T220901-636@post.gmane.org \
--to=jan.steinke@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
Powered by JetHome