From: "Stephen C. Tweedie" <sct@redhat.com>
To: Phil Schwan <pschwan@cmu.edu>
Cc: sct@redhat.com, linux-mm@kvack.org
Subject: Re: buffer/page cache patches
Date: Fri, 23 Apr 1999 11:58:51 +0100 (BST) [thread overview]
Message-ID: <14112.21099.599776.829643@dukat.scot.redhat.com> (raw)
In-Reply-To: <19990422211814.I24095@cmu.edu>
Hi,
On Thu, 22 Apr 1999 21:18:14 -0400, Phil Schwan <pschwan@cmu.edu> said:
> You mentioned that the patches that are going to go into 2.3 have
> already in fact been written. Are these available for hacking and
> testing?
Somewhat, although they haven't been updated for the current 2.2
kernels. Eric Beiderman was maintaining that stuff and he's been
talking about getting it into shape for 2.3: ask on the
linux-mm@kvack.org mailing list to get in touch with all the people
involved.
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
parent reply other threads:[~1999-04-23 10:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <19990422211814.I24095@cmu.edu>]
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=14112.21099.599776.829643@dukat.scot.redhat.com \
--to=sct@redhat.com \
--cc=linux-mm@kvack.org \
--cc=pschwan@cmu.edu \
/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