From: Matthew Kennedy <mbkennedy@austin.rr.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-user] a preempt patch lament
Date: 27 Feb 2002 22:26:50 -0600 [thread overview]
Message-ID: <1014870410.26417.33.camel@gentoo.shacknet.nu> (raw)
In-Reply-To: <1014869691.24504.21.camel@kodiak.chronospace.org>
On Wed, 2002-02-27 at 22:14, Bruce A. Locke wrote:
> Anyone know if some kind soul is maintaining a preempt + tested XFS
> patch? With the dozens of different kernel trees these days someone has
> to be doing something like that :)
After playing around with a few patch sets, I think I'll move back to
gentoo's 2.4.17-r4 and wait for SGI to create a 2.4.18 patch set for XFS
(should be out any time). Then I'll apply the preempt patch to that and
see what happens. I too can't live with out that preempt patch... can't
imagine how I lived before it.
next prev parent reply other threads:[~2002-02-28 4:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1014865592.26121.27.camel@gentoo.shacknet.nu>
2002-02-28 4:14 ` [gentoo-dev] Re: [gentoo-user] a preempt patch lament Bruce A. Locke
2002-02-28 4:26 ` Matthew Kennedy [this message]
2002-03-01 18:03 ` Daniel Robbins
2002-03-01 19:20 Tod M.Neidt
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=1014870410.26417.33.camel@gentoo.shacknet.nu \
--to=mbkennedy@austin.rr.com \
--cc=gentoo-dev@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox