From: Arjan van de Ven <arjan@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@stusta.de>
Subject: Re: A proposal; making 2.6.20 a bugfix only version.
Date: Thu, 09 Nov 2006 20:21:55 +0100 [thread overview]
Message-ID: <1163100115.3138.524.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20061109111212.eee33367.akpm@osdl.org>
On Thu, 2006-11-09 at 11:12 -0800, Andrew Morton wrote:
> On Thu, 09 Nov 2006 10:52:00 +0100
> Arjan van de Ven <arjan@infradead.org> wrote:
>
> > Do you have the
> > impression that high quality bug reports on lkml (with this I mean ones
> > where there is sufficient information, which are not a request for
> > support and where the reporter actually answers questions that are asked
> > him) are not getting reasonable attention?
>
> Yes.
>
> And why does the report quality matter?
because it matters where people spend their time. And if you count
bugreports that are actually distro support questions and then say "but
these aren't looked at" it's not fair either.
> If there's insufficient info you
> just ask for more.
and that does happen. And half the time people just remain silent :(
I know I look at a whole bunch of bugreports in areas that I work on. I
see a lot of other people doing something similar. That doesn't mean
nothing slips through. I'm sure stuff does slip through. I would HOPE
it's really obscure things only; but I fear it's also cases where the
reporter didn't put the right people on the CC as well ;(
> But we all know that and nothing's going to happen so there's really not
> much point in discussing it. I have 270 saved-up-lkml-bug-reports to
> process.
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
next prev parent reply other threads:[~2006-11-09 19:22 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 22:09 Jesper Juhl
2006-11-08 22:22 ` Arjan van de Ven
2006-11-08 22:40 ` Jesper Juhl
2006-11-08 23:05 ` Andreas Mohr
2006-11-08 23:54 ` Jan Engelhardt
2006-11-10 15:15 ` Pavel Machek
2006-11-10 15:48 ` Horst H. von Brand
2006-11-15 21:04 ` Jesper Juhl
2006-11-08 22:51 ` Andrew Morton
2006-11-09 9:26 ` Arjan van de Ven
2006-11-09 9:36 ` Andrew Morton
2006-11-09 9:52 ` Arjan van de Ven
2006-11-09 19:12 ` Andrew Morton
2006-11-09 19:21 ` Arjan van de Ven [this message]
2006-11-09 21:11 ` Adrian Bunk
2006-11-09 21:31 ` Arjan van de Ven
2006-11-09 23:56 ` Thomas Gleixner
2006-11-10 0:18 ` Andrew Morton
2006-11-10 17:45 ` Stefan Richter
2006-11-11 11:00 ` Martin J. Bligh
2006-11-08 23:28 ` Diego Calleja
2006-11-09 6:48 ` Arjan van de Ven
2006-11-09 12:45 ` Rolf Eike Beer
2006-11-09 4:57 Al Boldi
2006-11-09 17:05 ` Stephen Hemminger
2006-11-10 15:52 ` Al Boldi
2006-11-10 16:16 ` Jesper Juhl
2006-11-10 16:42 ` Stephen Hemminger
2006-11-10 16:53 ` Randy Dunlap
2006-11-10 19:33 ` Al Boldi
2006-11-10 19:49 ` Arjan van de Ven
2006-11-10 21:22 ` Al Boldi
2006-11-10 21:31 ` Stephen Hemminger
2006-11-11 4:15 ` Al Boldi
2006-11-11 5:09 ` Stephen Hemminger
2006-11-11 7:23 ` David Miller
2006-11-11 11:15 ` Al Boldi
2006-11-11 6:31 ` Valdis.Kletnieks
2006-11-11 11:15 ` Al Boldi
2006-11-11 7:15 ` Willy Tarreau
2006-11-11 12:03 ` Neil Brown
2006-11-11 19:16 ` Krzysztof Halasa
2006-11-11 19:15 ` Adrian Bunk
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=1163100115.3138.524.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®