From: DaMouse Networks <damouse@ntlworld.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.1-rc1-mjb1
Date: Sun, 4 Jan 2004 11:36:30 +0000 [thread overview]
Message-ID: <20040104113630.78a94dcd@EozVul.WORKGROUP> (raw)
I'm just wondering how the HT schedular merge is coming? I'm interesting in getting a better/new one for some testing so I wondered how it was coming along with it being ported to 2.6.1-rc1.
-DaMouse
next reply other threads:[~2004-01-04 11:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 11:36 DaMouse Networks [this message]
2004-01-04 16:04 ` 2.6.1-rc1-mjb1 Martin J. Bligh
-- strict thread matches above, loose matches on Subject: below --
2004-01-03 0:42 2.6.1-rc1-mjb1 Martin J. Bligh
2004-01-04 1:40 ` 2.6.1-rc1-mjb1 Marcos D. Marado Torres
2004-01-04 1:48 ` 2.6.1-rc1-mjb1 Martin J. Bligh
2004-01-04 11:47 ` 2.6.1-rc1-mjb1 Mike Fedyk
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=20040104113630.78a94dcd@EozVul.WORKGROUP \
--to=damouse@ntlworld.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.