Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ulrich Teichert <ut@netsurf.de>
To: spock@mgnet.de (Klaus Naumann)
Cc: linux-mips@oss.sgi.com, linux-mips@fnet.fr
Subject: Re: Bug Tracker online
Date: Sun, 22 Oct 2000 13:45:00 +0200 (MEST)	[thread overview]
Message-ID: <200010221145.NAA01415@netsurf.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0010221242002.8799-100000@spock.mgnet.de> from "Klaus Naumann" at Oct 22, 2000 12:52:23 PM

Hi!

>> I think it is really useful to know what configurations / kernel versions
>> and hardware other people have. I have published the bootlogs of
>> my DECStations on my website. 
>
>ok, we just need to think about a good way to make the thing happen.
>Anyone with a good idea mail me ;)

Couldn't we just take the bug tracker? I mean, add a state to the bugs,
abuse a text field, et voila.

HTH,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Paralysed (The Sewergrooves),
24539 Neumuenster, Germany|Cheap Excitement (Stratford Mercenaries)

WARNING: multiple messages have this Message-ID (diff)
From: Ulrich Teichert <ut@netsurf.de>
To: Klaus Naumann <spock@mgnet.de>
Cc: linux-mips@oss.sgi.com, linux-mips@fnet.fr
Subject: Re: Bug Tracker online
Date: Sun, 22 Oct 2000 13:45:00 +0200 (MEST)	[thread overview]
Message-ID: <200010221145.NAA01415@netsurf.de> (raw)
Message-ID: <20001022114500.PVmi167ayR92uBoFkK9tCfc_IG3N8qn30L6HvpeI-C4@z> (raw)
In-Reply-To: <Pine.LNX.4.21.0010221242002.8799-100000@spock.mgnet.de> from "Klaus Naumann" at Oct 22, 2000 12:52:23 PM

Hi!

>> I think it is really useful to know what configurations / kernel versions
>> and hardware other people have. I have published the bootlogs of
>> my DECStations on my website. 
>
>ok, we just need to think about a good way to make the thing happen.
>Anyone with a good idea mail me ;)

Couldn't we just take the bug tracker? I mean, add a state to the bugs,
abuse a text field, et voila.

HTH,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Paralysed (The Sewergrooves),
24539 Neumuenster, Germany|Cheap Excitement (Stratford Mercenaries)

  reply	other threads:[~2000-10-22 11:46 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 [this message]
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=200010221145.NAA01415@netsurf.de \
    --to=ut@netsurf.de \
    --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