Linux MIPS Architecture development
 help / color / mirror / Atom feed
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: Sun, 22 Oct 2000 12:30:13 +0200	[thread overview]
Message-ID: <20001022123012.A1564@paradigm.rfc822.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0010220951060.4857-100000@spock.mgnet.de>; from spock@mgnet.de on Sun, Oct 22, 2000 at 10:04:27AM +0200

On Sun, Oct 22, 2000 at 10:04:27AM +0200, Klaus Naumann wrote:
> Actually writing the bug tracker wasn't an act of boredom 
> (if you meant it that way). I had the strong feeling that we have

No - I didnt think of it that way ...

> > 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.
> 
> This is indeed a interesting idea. Writing it wouldn't be a big deal.
> But the question is if it's worth writing it. First we would need
> some ppl which actally send the info somewhere - I'm pretty
> much in doubt, that we will find enough so that it rents.
> Second question is if ppl are actually interested in such a thing.
> I'll not again waste time writing something where I don't get at least a
> small ammount of feedback and which noone is using.

Right - I just thought as a feedback for the kernel cvs commits the other
way round that you implemented - Sometimes (most of the time ?) bugs
keep not found because noone is using some specific feature (Like the
Timeing stuff in the decstations) and though a lot of people simply
think its their fault instead of complaining - But with something like
that and possibly a simple shell script we yould collect not negative
but positive information on WHAT is actually working. Nevertheless this
only works for a small subset of the mips stuff (kernel) and though might
be pretty useless as most of the kernel stuff works and userspace is
getting the problem.

Flo
-- 
Florian Lohoff		flo@rfc822.org		      	+49-5201-669912
      "Write only memory - Oops. Time for my medication again ..."

  parent reply	other threads:[~2000-10-22 10:32 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
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     ` Florian Lohoff [this message]
2000-10-22  8:25 ` Bug Tracker online 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=20001022123012.A1564@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