From: Samium Gromoff <deepfire@sic-elvis.zel.ru>
To: linux-kernel@vger.kernel.org
Cc: Nick Piggin <piggin@cyberone.com.au>, Andrew Morton <akpm@osdl.org>
Subject: Re: [TEST] 2.4 vs 2.6.2 vs 2.6.2-mm1 vs 2.6.2-rc3-mm1
Date: Mon, 09 Feb 2004 18:46:29 +0300 [thread overview]
Message-ID: <87znbsxnl6.wl@canopus.ns.zel.ru> (raw)
In-Reply-To: <873c9kz4et.wl@canopus.ns.zel.ru>
At Mon, 09 Feb 2004 17:57:46 +0300,
Samium Gromoff wrote:
[snip]
> the kernels were:
> 2.4.20-pre9, 2.6.2 -- no comments
> 2.6.2-rc3-mm1 -- that one didn`t include the Namesys VM patches
> 2.6.2--mm1 -- that one _did_ include the Namesys VM patches
Small correction -- these are not exactly the Namesys patches, they are
from Nick Piggin (http://www.kerneltrap.org/~npiggin/vm/), and some are
certainly based on the Namesys folks` work...
[snip]
> regards, Samium Gromoff
next prev parent reply other threads:[~2004-02-09 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 14:57 [TEST] 2.4 vs 2.6.2 vs 2.6.2-mm1 vs 2.6.2-rc3-mm1 Samium Gromoff
2004-02-09 15:46 ` Samium Gromoff [this message]
2004-02-10 12:53 ` Nick Piggin
2004-02-10 13:33 ` Samium Gromoff
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=87znbsxnl6.wl@canopus.ns.zel.ru \
--to=deepfire@sic-elvis.zel.ru \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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