Re: Raw data from dedicated kernel bug database

[John Bradford <john@grabjohn.com>]

> What are the chances that the raw data from the kernel bugdb could be
> made available?  I bet Bradford wants it and I know I want.
                         ^^^^^^^^

I do have a first name, you know :-).

It would be nice to have some more bugs listed in my new database - at
the moment there is only one, but I was reluctant to spend time
manually filling it, when that time could be better spent improving
the system itself.

Importing the existing data in to my database isn't going to
automatically give you all of the advantages of it, because it's
ability to search via config options, and track version information
obviously relies on that information being present, but it would be
simple enough for someone, (me, if nobody else is interested), to add
it one the database is populated.

I'm working on adding more features at the moment, but if you've got
feedback, (positive or negative), please let me hear it - traffic to
it has been pretty high, but I'm not getting much mail about it.

Personally, I think the ability to upload your .config file, and have
it say, "OK, the following bugs are known to be triggered by those
options", and to have a colour-coded table of
working/broken/untested/can't test kernel versions for each bug could
potentially save us all loads of work, but if you disagree, just let
me know.

> To calm any fears that we are trying to take over the bugdb, we're not.
> We just want to track it.  Any changes made in a BK bugdb are trivially
> exportable to an external format and if the need arises we'll work with
> IBM/OSDL to make that happen.  In fact, we can automate it.

Let me know if I can add some kind of export function to my DB that
will help BK users, Larry^WMcVoy, and I'll consider it.

John.