From: John Bradford <john@grabjohn.com>
To: greg@kroah.com (Greg KH)
Cc: linux-kernel@vger.kernel.org
Subject: Re: New kernel bug database on-line
Date: Tue, 31 Dec 2002 08:53:58 +0000 (GMT) [thread overview]
Message-ID: <200212310853.gBV8rwpf000393@darkstar.example.net> (raw)
In-Reply-To: <20021231005103.GG814@kroah.com> from "Greg KH" at Dec 30, 2002 04:51:03 PM
>
> On Mon, Dec 30, 2002 at 11:59:59PM +0000, John Bradford wrote:
> > 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/
>
> Hm, on this page it says the latest Development kernel is 2.5.54, does
> this database travel forward in time? :)
Yeah, I said it had some good features :-)
> > 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:
>
> Automated account creation should be your first new feature you add to
> this program, almost no one will use this if you make them do that.
The server runs about 100 other websites, and I had visions of it
getting posted to Slashdot... Besides, I finished the code at about
11 PM yesterday, I want to have a look at it again this morning to
check for security holes before everybody r00ts the box :-).
John.
prev parent reply other threads:[~2002-12-31 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 23:59 New kernel bug database on-line John Bradford
2002-12-31 0:51 ` Greg KH
2002-12-31 8:53 ` John Bradford [this message]
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=200212310853.gBV8rwpf000393@darkstar.example.net \
--to=john@grabjohn.com \
--cc=greg@kroah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.