From: Mike Fedyk <mfedyk@matchmail.com>
To: Xose Vazquez Perez <xose@wanadoo.es>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Merge more VM from 2.4-aa? was: Linux 2.4.24-pre2
Date: Mon, 22 Dec 2003 13:23:44 -0800 [thread overview]
Message-ID: <20031222212344.GS6438@matchmail.com> (raw)
In-Reply-To: <3FE759A4.50208@wanadoo.es>
On Mon, Dec 22, 2003 at 09:52:52PM +0100, Xose Vazquez Perez wrote:
> Mike Fedyk wrote:
>
> > Do you plan on merging any more of the VM from Andrea in this release (or
> > future releases)?
>
> Andrea said [1] that there are two patches missing: inode-highmem and
> related_bhs
> But he is not going to work on it for 2.4
>
> [1] http://marc.theaimsgroup.com/?l=linux-kernel&m=107048611507709&w=2
Yes, I read this one when it was posted, but forgot the details. It seems
that inode-highmem is relatively self contained though.
next prev parent reply other threads:[~2003-12-22 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 20:52 Merge more VM from 2.4-aa? was: Linux 2.4.24-pre2 Xose Vazquez Perez
2003-12-22 21:23 ` Mike Fedyk [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-22 19:55 Marcelo Tosatti
2003-12-22 20:31 ` Merge more VM from 2.4-aa? was: " Mike Fedyk
2003-12-22 22:36 ` Marcelo Tosatti
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=20031222212344.GS6438@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xose@wanadoo.es \
/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