From: "Markus Hästbacka" <midian@ihme.org>
To: Timothy Miller <miller@techsource.com>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Nick's scheduler v19a
Date: Fri, 21 Nov 2003 19:00:35 +0200 [thread overview]
Message-ID: <1069434035.21039.5.camel@midux> (raw)
In-Reply-To: <3FBE3B0D.8030501@techsource.com>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
Yes, but how could I know if the bug is in XFree86? in kernel? in the
nvidia driver module? and no, I can't even hope to try to reproduce bugs
without nvidia module, because no X => no bugs. If you tell me what I
need to add to kernel configuration to get some info while something
happens, I'll probably try to reproduce bugs when test10 is out with
vanilla kernel.
And yes, I'm intrested in the performance of other's computers too, but
if this is new then it's new, and I can't by my self know where the bug
(maybe) is.
Regards,
Markus
On Fri, 2003-11-21 at 18:19, Timothy Miller wrote:
> Markus Hästbacka wrote:
> > That may be true, but why should I complain anymore? Nick made a really
> > great patch that makes things working for me.
> >
>
>
> Are you interested only in the performance of your own computer, or do
> you have any interest in the performance of other people's computers as
> well?
>
> If there's a bug, there's a bug, and you've identified it. Contrary to
> the attitude of our friends in Redmond, the open source community tends
> to see bugs as being really evil. If you've found a bug, we want to
> investigate it and fix it.
--
"Software is like sex, it's better when it's free."
Markus Hästbacka <midian at ihme.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-11-21 17:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-15 13:11 Nick's scheduler v19a Nick Piggin
2003-11-20 20:45 ` Markus Hästbacka
2003-11-20 23:34 ` Nick Piggin
2003-11-21 6:11 ` Markus Hästbacka
2003-11-21 6:20 ` Nick Piggin
2003-11-21 9:06 ` Markus Hästbacka
2003-11-21 9:14 ` Nick Piggin
2003-11-21 9:32 ` Markus Hästbacka
2003-11-21 9:54 ` Måns Rullgård
2003-11-21 10:21 ` Markus Hästbacka
2003-11-21 16:19 ` Timothy Miller
2003-11-21 17:00 ` Markus Hästbacka [this message]
2003-11-24 7:45 ` Peter C. Ndikuwera
2004-01-12 19:40 ` Bug found (Was: Re: Nick's scheduler v19a) Markus Hästbacka
2003-12-03 16:14 ` Nick's scheduler v19a Markus Hästbacka
2003-12-03 22:15 ` Nick Piggin
2003-12-07 21:52 ` Markus Hästbacka
2003-12-07 23:05 ` Nick Piggin
[not found] <3FF79C54.4070200@cyberone.com.au>
2004-02-02 11:21 ` Markus Hästbacka
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=1069434035.21039.5.camel@midux \
--to=midian@ihme.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
/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