From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
Cc: Stephen Thomas <stephen.thomas@insignia.co.uk>,
linux-mm <linux-mm@kvack.org>
Subject: Re: Ideas for memory management hackers.
Date: Tue, 9 Dec 1997 12:45:21 -0500 (U\x01) [thread overview]
Message-ID: <Pine.LNX.3.95.971209124434.11334C-100000@as200.spellcast.com> (raw)
In-Reply-To: <Pine.LNX.3.91.971209154819.584H-100000@mirkwood.dummy.home>
...
> I think I'll send it to Linus (together with Zlatko's
> big-order hack) as a bug-fix (we're on feature-freeze after all:)
> for inclusion in 2.1.72...
Hrmpf - what is Zlatko's big-order hack?
-ben
next prev parent reply other threads:[~1997-12-09 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <348D3B36.673BEE82@nospam.isltd.insignia.co.uk>
1997-12-09 14:53 ` Rik van Riel
1997-12-09 16:11 ` Dr. Werner Fink
1997-12-09 17:10 ` Rik van Riel
1997-12-10 13:13 ` Zlatko Calusic
1997-12-10 15:21 ` Dr. Werner Fink
1997-12-10 19:13 ` Benjamin C.R. LaHaise
1997-12-10 21:55 ` Rik van Riel
1997-12-09 17:45 ` Benjamin C.R. LaHaise [this message]
1997-12-09 17:53 ` Rik van Riel
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.95.971209124434.11334C-100000@as200.spellcast.com \
--to=blah@kvack.org \
--cc=H.H.vanRiel@fys.ruu.nl \
--cc=linux-mm@kvack.org \
--cc=stephen.thomas@insignia.co.uk \
/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