From: Andrew Morton <akpm@osdl.org>
To: tglx@linutronix.de
Cc: Arjan van de Ven <arjan@infradead.org>,
Adrian Bunk <bunk@stusta.de>, Jesper Juhl <jesper.juhl@gmail.com>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: A proposal; making 2.6.20 a bugfix only version.
Date: Thu, 9 Nov 2006 16:18:13 -0800 [thread overview]
Message-ID: <20061109161813.5f0c706a.akpm@osdl.org> (raw)
In-Reply-To: <1163116618.8335.173.camel@localhost.localdomain>
On Fri, 10 Nov 2006 00:56:58 +0100
Thomas Gleixner <tglx@linutronix.de> wrote:
> On Thu, 2006-11-09 at 22:31 +0100, Arjan van de Ven wrote:
> > > Since the first list I sent immediately after 2.6.19-rc1 was released,
> > > kernel Bugzilla #7255 is part of my list of 2.6.19-rc regressions but
> > > has gotten exactly zero developer responses.
> >
> > where was the lkml mail for this?
> >
> > >
> > > What exactly were the mistakes of the submitter resulting in noone
> > > caring about Bugzilla #7255?
> >
> > he didn't post to lkml?
>
> That's no excuse, as Adrian pointed it out on LKML since weeks.
>
> Also the kernel.org bugzilla has a real flaw:
>
> There is no way to get informed of new entries automatically and
> filtered by Category and Component. At least I did not find a way and
> bugme-admin@osdl.org seems to be a black hole.
>
> The result is that you have to go to bugzilla on a regular base instead
> of getting automatic notifications of new entries. I do it once in a
> while, but it is really ineffective.
>
I screen all bugzilla reports and I ensure that any of them which look like
they're real and which have a breathing maintainer are brought to that
maintainer's attention.
So no, I think the number of bugs in bugzilla which the relevant maintainer
didn't hear about is vanishingly small.
next prev parent reply other threads:[~2006-11-10 0:21 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
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 [this message]
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=20061109161813.5f0c706a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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®