From: John Bradford <john@grabjohn.com>
To: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] Kernel Bug Database 2.0
Date: Fri, 17 Jan 2003 23:12:56 +0000 (GMT) [thread overview]
Message-ID: <200301172312.h0HNCuHO002622@darkstar.example.net> (raw)
I've been working on it all day, and I've finally got version 2.0
ready and working, and put it on-line:
http://grabjohn.com/kernelbugdatabase
I've added a major new concept in this version - bug reports and
confirmed bugs, (I.E. bugs which are being actively investigated by
somebody with administrative access to the Kernel Bug Database), are
now separate things.
In other words, anybody can submit a bug report, but only designated
people can collect those reports together into a confirmed bug. A bug
report can be related to several confirmed bugs. Confirmed bugs can
be read and commented on by all users.
Thanks to Fergal Daly for submitting this idea, and I'd also like to
point out that I read more or less the same idea in this email by
Larry McVoy, where Jens mentions the idea of sorting a queue of new
bugs into the real database.
http://www.cs.helsinki.fi/linux/linux-kernel/2001-13/0084.html
Hopefully this system also makes Alan's idea of keeping all bug
reports for data mining, (also mentioned above), more practical.
I haven't written any documentation for it yet, but hopefully it's
fairly self-explanatory anyway.
I've added a single confirmed bug, which relates to two vaguely
related bug reports, (missing help text, and a missing comment), but
anybody who wants administrative access to add and modify confirmed
bugs, just drop me an E-Mail.
As always, any feedback on this would be much appreciated.
John.
reply other threads:[~2003-01-17 23:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200301172312.h0HNCuHO002622@darkstar.example.net \
--to=john@grabjohn.com \
--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
all inboxes | Powered by JetHome®