From: Tupshin Harper <tupshin@tupshin.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: lkml, bugme.osdl.org?
Date: Tue, 03 Dec 2002 10:09:14 -0800 [thread overview]
Message-ID: <3DECF34A.3000407@tupshin.com> (raw)
In-Reply-To: <20021203121521.GB30431@suse.de>
The bugzillla Dave Jones wrote:
>whilst on the subject of bugzilla:
>a few people (myself included) go through the bug database once a week
>or so pruning out-of-date/fixed entries. So far the ones I've closed have
>been quite sensible, but there are a few there of the form..
>
>"xxx doesn't work in 2.5.47", then Rusty's module rewrite happened,
>and the tester didn't (or couldn't) see if it got fixed in subsequent
>kernels. I'll send out pings to such reports when they get to something
>like 5 kernels old. If the problem then doesn't get re-ACKed, I'll
>close it. Any objections?
>
> Dave
>
Thankfully osdl has been set up with very useful fields for such things.
It sounds like cases that you are describing should be rejected with a
status of either "UNREPRODUCIBLE" if the bug report was decently done,
but you can't reproduce it, or "INSUFFICIENT_DATA" if the bug report was
filed inadequately. This can serve as a prompt to the original filer to
re-open it with better data.
I don't think you should hesitate to do that at least once for a bug
fits either of those cases.
-Tupshin
next prev parent reply other threads:[~2002-12-03 17:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 7:24 Valdis.Kletnieks
2002-12-03 12:15 ` Dave Jones
2002-12-03 14:13 ` bill davidsen
2002-12-03 18:09 ` Tupshin Harper [this message]
2002-12-04 11:58 ` Dr. David Alan Gilbert
2002-12-04 12:35 ` Russell King
2002-12-04 12:42 ` Dave Jones
2002-12-04 18:32 ` Dr. David Alan Gilbert
2002-12-04 22:20 ` Russell King
2002-12-05 9:15 ` David Woodhouse
2002-12-05 9:25 ` William Lee Irwin III
2002-12-05 9:34 ` David Woodhouse
2002-12-05 9:35 ` William Lee Irwin III
2002-12-05 14:24 ` bill davidsen
2002-12-03 20:33 ` Martin J. Bligh
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=3DECF34A.3000407@tupshin.com \
--to=tupshin@tupshin.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=davej@codemonkey.org.uk \
--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