From: Andrew Morton <akpm@linux-foundation.org>
To: Daniel Walker <dwalker@mvista.com>
Cc: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>,
"Björn Steinbrink" <B.Steinbrink@gmx.de>,
eranian@hpl.hp.com, ak@suse.de, linux-kernel@vger.kernel.org,
"Natalie Protasevich" <protasnb@gmail.com>
Subject: Re: Who wants to maintain KR list for stable releases? (was Re: nmi_watchdog=2 regression in 2.6.21)
Date: Mon, 27 Aug 2007 11:26:07 -0700 [thread overview]
Message-ID: <20070827112607.aafdaee9.akpm@linux-foundation.org> (raw)
In-Reply-To: <1188234515.2435.243.camel@dhcp193.mvista.com>
On Mon, 27 Aug 2007 10:08:34 -0700
Daniel Walker <dwalker@mvista.com> wrote:
> On Mon, 2007-08-27 at 09:44 -0700, Andrew Morton wrote:
>
> > It's a hassle when someone doesn't have a bugzilla account. But there are
> > humans sitting behind bugzilla handling stuff (fsvo "human"). I've already
> > forwarded your bugzilla report to Stephane pointing out that he doesn't
> > have an account.
> >
> > I screen 100% of new bugzilla reports and for those which I think need
> > attention (most), I will ensure that the appropriate parties get to see the
> > report. I'll also verify that the "regression" state is correct and that
> > the provided info is sufficient-looking. (It's amazing how many people
> > have trouble with the "Most recent kernel where this bug did not occur:"
> > question).
>
> When I read that question, it sort of feels like a mind bender. It's the
> "did not occur" , most people are thinking "which version of the kernel
> did I find this in", but it's asking the opposite ..
We've already reworked that question once because poeple were mucking up
the answer. Without a lot of success.
Maybe it should be "Is this bug a regression? If so, what was the most
recent kernel which didn't have this bug?". But that requires that people
know what "regression" means.
Bearing in mind that many reporters aren't native English speakers, I'm
really struggling to find a simple and robust way to ask this question.
Maybe "Did any previous kernel work OK? If so, what was the most recent
version of the kernel which didn't have this bug?"
hrm. It doesn't matter much, really. When people muck it up (or just
fail to answer that question) I go back and ask them again. It only
takes 30 seconds...
> For bug #8945 I really don't recall the version of the kernel I ran when
> it worked .. I had to do a bisect to get some clue about that ..
> nmi_watchdog isn't something I use every time I boot (I should tho), and
> I go through lots of kernels ..
>
> > What I haven't been doing is ensuring that the Product and Component fields
> > are suitably set. That's something which Natalie is now cleaning up.
>
> In terms of regressions, it would be nice for the "Version" field to be
> the kernel where the regression first showed up .. Like on bug #8945 I
> put in 2.6.22 even tho I found the issue in 2.6.23-rc1 .. Is that
> typically what the "Version" field is used for?
Natalie is spending quite a bit of time with the bugzilla metadata,
queries, etc. I'll shut up and let her tell us what changes we need in
this area.
next prev parent reply other threads:[~2007-08-27 18:32 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 0:06 nmi_watchdog=2 regression in 2.6.21 Daniel Walker
2007-08-08 14:20 ` Björn Steinbrink
2007-08-08 15:20 ` Daniel Walker
2007-08-20 16:44 ` Daniel Walker
2007-08-23 20:08 ` Michal Piotrowski
2007-08-23 21:22 ` Daniel Walker
2007-08-27 0:45 ` Who wants to maintain KR list for stable releases? (was Re: nmi_watchdog=2 regression in 2.6.21) Michal Piotrowski
2007-08-27 7:51 ` Andrew Morton
2007-08-27 9:41 ` Jeff Garzik
2007-08-27 11:35 ` Michal Piotrowski
2007-08-27 16:09 ` Adrian Bunk
2007-08-27 16:05 ` Daniel Walker
2007-08-27 11:38 ` Michal Piotrowski
2007-08-27 12:35 ` Rafael J. Wysocki
2007-08-27 15:02 ` Michal Piotrowski
2007-08-27 15:13 ` Daniel Walker
2007-08-27 15:26 ` Michal Piotrowski
2007-08-27 15:39 ` Daniel Walker
2007-08-27 17:02 ` Michal Piotrowski
2007-08-27 17:17 ` Daniel Walker
2007-08-27 19:12 ` David Rees
2007-08-29 7:42 ` Natalie Protasevich
2007-08-29 22:23 ` Adrian Bunk
2007-08-29 23:59 ` Natalie Protasevich
2007-08-30 8:51 ` Adrian Bunk
2007-08-30 15:24 ` Who wants to maintain KR list for stable releases? Stefan Richter
[not found] ` <32209efe0708300950r5787402l4d02cedd862314fd@mail.gmail.com>
2007-08-30 22:11 ` Al Boldi
2007-09-03 12:29 ` Adrian Bunk
2007-09-03 13:20 ` Stefan Richter
2007-08-30 15:54 ` Who wants to maintain KR list for stable releases? (was Re: nmi_watchdog=2 regression in 2.6.21) Bill Davidsen
2007-09-03 12:43 ` Adrian Bunk
2007-08-27 16:26 ` Daniel Walker
2007-08-27 16:44 ` Andrew Morton
2007-08-27 16:52 ` Adrian Bunk
2007-08-27 17:08 ` Daniel Walker
2007-08-27 18:26 ` Andrew Morton [this message]
2007-08-27 8:11 ` David Rees
2007-08-27 11:42 ` Michal Piotrowski
2007-08-27 14:39 ` Daniel Walker
2007-08-27 15:11 ` Michal Piotrowski
2007-08-27 17:54 ` nmi_watchdog=2 regression in 2.6.21 Stephane Eranian
2007-08-27 17:55 ` Daniel Walker
2007-08-27 22:55 ` Stephane Eranian
2007-08-27 23:07 ` Daniel Walker
2007-08-28 9:12 ` Stephane Eranian
2007-08-28 14:34 ` Daniel Walker
2007-08-28 17:05 ` Stephane Eranian
2007-08-28 18:30 ` Daniel Walker
2007-08-28 19:46 ` Stephane Eranian
2007-08-28 20:13 ` Daniel Walker
2007-08-29 21:24 ` Stephane Eranian
2007-08-30 1:21 ` Daniel Walker
2007-08-30 21:05 ` Stephane Eranian
2007-08-31 14:43 ` Daniel Walker
2007-08-31 16:21 ` Stephane Eranian
2007-08-31 16:35 ` Daniel Walker
2007-08-31 18:06 ` Björn Steinbrink
2007-09-01 0:24 ` Daniel Walker
2007-09-01 1:00 ` Björn Steinbrink
2007-09-01 1:36 ` Daniel Walker
2007-09-01 10:19 ` Andi Kleen
2007-09-01 19:51 ` Stephane Eranian
2007-09-01 20:32 ` Andi Kleen
2007-09-01 20:46 ` Daniel Walker
2007-09-01 9:12 ` Andi Kleen
2007-08-28 20:26 ` Daniel Walker
2007-08-28 20:21 ` Stephane Eranian
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=20070827112607.aafdaee9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=B.Steinbrink@gmx.de \
--cc=ak@suse.de \
--cc=dwalker@mvista.com \
--cc=eranian@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=protasnb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox