From: "Douglas J. Hunley" <root@hunley.homeip.net>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.5pre2aa1
Date: Wed, 16 May 2001 11:08:01 -0400 [thread overview]
Message-ID: <0105161108010L.00722@hunley.homeip.net> (raw)
In-Reply-To: <20010515235916.B2415@athlon.random> <Pine.LNX.4.21.0105152039060.4671-100000@imladris.rielhome.conectiva> <20010516155253.A15796@athlon.random>
In-Reply-To: <20010516155253.A15796@athlon.random>
On Wednesday 16 May 2001 09:52, Andrea Arcangeli babbled:
> > These descriptions are very helpful. Are they available somewhere
>
personally, I wish all kernel announcements were as nice as this. Kudos to
Andrea.
--
Douglas J. Hunley (Linux User #174778)
http://hunley.homeip.net/ http://linux.nf/ http://www.kicq.org/
And on the 8th day God said, "OK Murphy, you take over."
prev parent reply other threads:[~2001-05-16 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-15 21:59 2.4.5pre2aa1 Andrea Arcangeli
2001-05-15 23:42 ` 2.4.5pre2aa1 Rik van Riel
2001-05-16 13:52 ` 2.4.5pre2aa1 Andrea Arcangeli
2001-05-16 15:08 ` Douglas J. Hunley [this message]
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=0105161108010L.00722@hunley.homeip.net \
--to=root@hunley.homeip.net \
--cc=andrea@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox