From: John Bradford <john@grabjohn.com>
To: jbglaw@lug-owl.de (Jan-Benedict Glaw)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Kernel Bug Database V1.10 on-line
Date: Thu, 9 Jan 2003 14:40:47 +0000 (GMT) [thread overview]
Message-ID: <200301091440.h09Eeln1001368@darkstar.example.net> (raw)
In-Reply-To: <20030109134755.GE2529@lug-owl.de> from "Jan-Benedict Glaw" at Jan 09, 2003 02:47:55 PM
> > Version 1.10 of my kernel bug database is now on-line at:
> > http://grabjohn.com/kernelbugdatabase/
>
> > If the original submitter of a bug uploaded their config file, you can
> > download a config file with the same options set.
>
> What do I get? His/her config file, or some other?
No, you don't just get a copy of the original config file:
When a config file is uploaded to the system, it's parsed and the
actual config options are stored in a database. If comments are
present in a form that resembles what the existing kernel
configurators use to indicate different sections, then those comments
are used to categorise the config options in the database.
The main reason for this is so that if somebody reports a bug, and
includes their config information, a developer can select one of their
config options from a list, and indicate that the bug is triggered by
it.
Re-generating the config file from that database, so that somebody
else can download it was added as an afterthought :-). Comments are
re-inserted, as well as an additional comment showing which kernel
version the config was originally intended for.
> One can watch certain subsystems/drivers. That's a _really_ nice
> feature, and I'd even like to be notified if a file belonging to one of
> "my" choosen subsystems is to be changed on mainstream. However,
> choosing subsystems of interest isn't quite fun because of the entrie's
> order.
>
> I'd do this with three parts (within one list):
>
> ARCH - ALPHA
> ARCH - SPARC
> ARCH - ...
>
> Then important subsystems:
> FS-Core
> INIT
> NET
> NET-IPv4
> NET-IPv6
> NET-xxx
> PCI
> SCSI
> IDE
> =2E..
>
> =2E..and at last, I'd list all chooseable drivers:
> 3c509
> cpuid
> ACPI
> APM
> FS - AFS
> FS - EXT2
> FS - EXT3
> FS - codepages
> =2E..
Well, at the moment, the list is just generated from the MAINTAINERS
file, I didn't want to introduce my own grouping of things, but it
really depends on what people want.
I could add the ability to watch via config options as well as the
list of maintainers, would that be helpful?
> That would really ease finding the interesting parts. Where, for
> example, can I go for sparc?
Hmm, good point, there is only an UltraSPARC maintainer listed. The
problem is, this is a problem with the MAINTAINERS file that my
database has inherited - do we fix the MAINTAINERS file or my db?
John.
prev parent reply other threads:[~2003-01-09 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 13:11 [ANNOUNCE] Kernel Bug Database V1.10 on-line John Bradford
2003-01-09 13:22 ` Ingo Molnar
2003-01-09 13:30 ` John Bradford
2003-01-09 13:52 ` Alex Riesen
2003-01-09 14:42 ` John Bradford
2003-01-09 13:47 ` Jan-Benedict Glaw
2003-01-09 14:40 ` 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=200301091440.h09Eeln1001368@darkstar.example.net \
--to=john@grabjohn.com \
--cc=jbglaw@lug-owl.de \
--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