From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Kernel Bug Database V1.10 on-line
Date: Thu, 9 Jan 2003 14:47:55 +0100 [thread overview]
Message-ID: <20030109134755.GE2529@lug-owl.de> (raw)
In-Reply-To: <200301091311.h09DB4Ka001126@darkstar.example.net>
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
On Thu, 2003-01-09 13:11:04 +0000, John Bradford <john@grabjohn.com>
wrote in message <200301091311.h09DB4Ka001126@darkstar.example.net>:
> 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?
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
...
...and at last, I'd list all chooseable drivers:
3c509
cpuid
ACPI
APM
FS - AFS
FS - EXT2
FS - EXT3
FS - codepages
...
That would really ease finding the interesting parts. Where, for
example, can I go for sparc?
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur
fuer einen Freien Staat voll Freier Bürger" | im Internet!
Shell Script APT-Proxy: http://lug-owl.de/~jbglaw/software/ap2/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-09 13:39 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 [this message]
2003-01-09 14:40 ` 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=20030109134755.GE2529@lug-owl.de \
--to=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