From: Arjan van de Ven <arjanv@redhat.com>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Rik van Riel <riel@conectiva.com.br>,
Arjan van de Ven <arjanv@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: TUX development? Anyone?
Date: Fri, 15 Feb 2002 13:45:15 -0500 [thread overview]
Message-ID: <20020215134515.A4508@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0202151638570.12554-100000@imladris.surriel.com> <Pine.LNX.4.30.0202151942220.21207-100000@mustard.heime.net>
In-Reply-To: <Pine.LNX.4.30.0202151942220.21207-100000@mustard.heime.net>; from roy@karlsbakk.net on Fri, Feb 15, 2002 at 07:44:05PM +0100
On Fri, Feb 15, 2002 at 07:44:05PM +0100, Roy Sigurd Karlsbakk wrote:
> > So why haven't you ? Or do you not count as "someone" ? ;)
>
> I happen to be in the rather large group of people not very familiar with
> the linux kernel source code.
>
> > I guess Ingo might just have been busy working on the O(1)
> > scheduler, or something.
>
> Please try to understand that banging my head against a problem for (now
> over a month) is quite annoying.
You know what...... that's what support is for.
next prev parent reply other threads:[~2002-02-15 18:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-15 13:21 TUX development? Anyone? Roy Sigurd Karlsbakk
2002-02-15 13:57 ` Arjan van de Ven
2002-02-15 18:32 ` Roy Sigurd Karlsbakk
2002-02-15 18:39 ` Rik van Riel
2002-02-15 18:44 ` Roy Sigurd Karlsbakk
2002-02-15 18:45 ` Arjan van de Ven [this message]
2002-02-15 18:59 ` How to make Linux/Tux/Whatever better? (was Re: TUX development? Anyone?) Roy Sigurd Karlsbakk
2002-02-15 19:11 ` Daniel Egger
2002-02-19 18:23 ` Ben Greear
2002-02-15 19:31 ` Rik van Riel
2002-02-16 5:42 ` Michael E Brown
2002-02-16 17:48 ` Horst von Brand
2002-02-15 22:52 ` TUX development? Anyone? Ingo Molnar
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=20020215134515.A4508@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=roy@karlsbakk.net \
/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