From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: linux-kernel <linux-kernel@vger.rutgers.edu>
Cc: linux-mm <linux-mm@kvack.org>
Subject: [patch *] vhand-2.1.65c released :)
Date: Mon, 24 Nov 1997 21:05:53 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.971124210032.4905B-100000@mirkwood.dummy.home> (raw)
Yup, I _am_ going for the record...
After receiving several messages about kswapd using too
much CPU time with my vhand-2.1.65b patch, I decided to
fix the problem and release the patch with linux-2.1.66
Since there was no linux(2.1.66) released this weekend,
and I still got messages from people, I decided to make
a new record: the highest number of patch-releases for
1 (development!) kernel-version...
And thus: vhand-2.1.65c saw the light :)
You can see the light too, at http://www.fys.ruu.nl/~riel/
grtz,
Rik.
----------
Send Linux memory-management wishes to me: I'm currently looking
for something to hack...
reply other threads:[~1997-11-24 20:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.3.91.971124210032.4905B-100000@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.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