All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Backlund <tmb@mandriva.org>
To: Robert Bradbury <robert.bradbury@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: RFC: Updating the LKML bug reporting/updating framework
Date: Mon, 26 Oct 2009 01:32:54 +0200	[thread overview]
Message-ID: <4AE4E026.9070402@mandriva.org> (raw)
In-Reply-To: <deaa866a0910251559r6c001e6ek553256ac8f81b1f7@mail.gmail.com>

Robert Bradbury wrote:
> Now, the LKML seems to to be a throwback almost to 1971 when the first
> email messages were sent between a couple of PDP-10s.  It has patches
> that I have no interest in, discussions I have no interest in and were
> it not for Gmail's search function it would be generally useless (very
> high Noise-to-Signal ratio).  Now maybe I do not understand the Linux
> development process.  Maybe this is a "Wizard of Oz" case and there is
> a hidden bug reporting system hidden behind the curtain -- but in
> spite of my best efforts I cannot locate it.

You didn't read http://www.kernel.org/  ??

There is a nice section on the first page stating:


Reporting Linux Kernel bugs

Please see http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html 
if you want to report a Linux kernel bug. Bug reports sent to the 
kernel.org administrators will be ignored.

There is now a bugzilla setup at bugzilla.kernel.org. Currently this is 
for reporting kernel version 2.6 bugs only.


--
Thomas

  reply	other threads:[~2009-10-25 23:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-25 22:59 RFC: Updating the LKML bug reporting/updating framework Robert Bradbury
2009-10-25 23:32 ` Thomas Backlund [this message]
2009-10-26 12:12   ` Robert Bradbury
2009-10-26 13:12     ` Frans Pop
2009-10-26 14:56     ` Theodore Tso
2009-10-26 18:40       ` Stefan Richter
2009-10-27  6:44     ` Pavel Machek

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=4AE4E026.9070402@mandriva.org \
    --to=tmb@mandriva.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.bradbury@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.