From: John Bradford <john@grabjohn.com>
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com, alan@lxorguk.ukuu.org.uk
Subject: New kernel bug database on-line
Date: Mon, 30 Dec 2002 23:59:59 +0000 (GMT) [thread overview]
Message-ID: <200212310000.gBV000hW004368@darkstar.example.net> (raw)
A couple of weeks ago, I started a thread about writing a bug database
dedicated to Linux kernel development.
My theory is that by making it Linux kernel development specific, it
can save more time, and make bug tracking easier than a generic bug
database.
Anyway, version 1.0 is now on-line:
http://grabjohn.com/kernelbugdatabase/
For the time being, you'll have to E-Mail me a request for a user
account, (which you need to do anything with it), but I've also put
some screenshots on-line here:
http://grabjohn.com/kernelbugdatabase/screenshots/
Basically, it's designed around two main principles:
* As much as possible is done automatically - you shouldn't need to
search using keywords, or categorise things manually, (although you
can). Instead, try searching for bugs by uploading a .config file,
and having it automatically parsed, by selecting config options from a
list, or by browsing the database for the state of bugs in a
particular kernel tree.
* Bugs are colour-coded:
Grey - untested in this kernel version
Blue - untestable in this kernel version due to other bugs
Red - this bug is present in this kernel
Green - this bug is not present in this kernel
There is also a command line interface, which will eventually be
accessible via E-Mail, but for the time being it is only accessible
via the web. The command line interface currently allows you to list
the bugs, get details about them, and add comments.
Any comments on this new bug database would be very much appreciated!
John
next reply other threads:[~2002-12-30 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 23:59 John Bradford [this message]
2002-12-31 0:51 ` New kernel bug database on-line Greg KH
2002-12-31 8:53 ` John Bradford
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=200212310000.gBV000hW004368@darkstar.example.net \
--to=john@grabjohn.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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