From: Florian Lohoff <flo@rfc822.org>
To: Klaus Naumann <spock@mgnet.de>
Cc: Linux/MIPS list <linux-mips@oss.sgi.com>,
"Linux MIPS fnet.fr" <linux-mips@fnet.fr>
Subject: Re: Bug Tracker online
Date: Sat, 21 Oct 2000 20:21:59 +0200 [thread overview]
Message-ID: <20001021202159.A3619@paradigm.rfc822.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0010201928160.8939-100000@spock.mgnet.de>; from spock@mgnet.de on Fri, Oct 20, 2000 at 07:45:22PM +0200
On Fri, Oct 20, 2000 at 07:45:22PM +0200, Klaus Naumann wrote:
> Hi all,
>
> I've written a bug tracker lately which is online as of now.
> It is intended to make it easier to track the problems of
> Linux/MIPS and to give the developers a more clear input and
> overview of the situation.
If you are bored - Would you mind writing a "Boot output parser".
What i have seen lately is that sometimes we are not aware of what
drivers/machines work and which dont. So i thought of an idea where
you just run a script or something sending something like
dmesg
cat /proc/cpuinfo
to a central location which than parses the output.
The one sending these reports has to give possible additional
hints on what he did/patch/change to get it to work. So probabably
we will than be able to keep track on which kernel versions
worked on which machines.
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
"Write only memory - Oops. Time for my medication again ..."
next prev parent reply other threads:[~2000-10-21 18:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-20 17:45 Bug Tracker online Klaus Naumann
2000-10-21 18:21 ` Florian Lohoff [this message]
2000-10-22 8:04 ` Klaus Naumann
2000-10-22 10:21 ` Karel van Houten
2000-10-22 10:21 ` Karel van Houten
2000-10-22 10:52 ` Klaus Naumann
2000-10-22 11:45 ` Ulrich Teichert
2000-10-22 11:45 ` Ulrich Teichert
2000-10-22 11:54 ` Klaus Naumann
2000-10-22 12:16 ` Ulrich Teichert
2000-10-22 12:16 ` Ulrich Teichert
2000-10-22 16:52 ` Ralf Baechle
2000-10-22 17:08 ` Karel van Houten
2000-10-22 17:08 ` Karel van Houten
2000-10-23 14:25 ` Florian Lohoff
2000-10-23 14:44 ` r8000 nick
2000-10-23 14:44 ` r8000 nick
2000-10-23 15:45 ` r8000 Florian Lohoff
2000-10-22 10:30 ` Bug Tracker online Florian Lohoff
2000-10-22 8:25 ` Guido Guenther
2000-10-22 8:58 ` Klaus Naumann
2000-10-22 9:02 ` Martin Schulze
2000-10-22 15:32 ` Keith M Wesolowski
2000-10-22 16:20 ` Klaus Naumann
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=20001021202159.A3619@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=spock@mgnet.de \
/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