From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: linux-mm <linux-mm@kvack.org>
Cc: linux-kernel <linux-kernel@vger.rutgers.edu>
Subject: mm patch developers' homepage
Date: Wed, 10 Dec 1997 04:53:54 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.971210044815.5196B-100000@mirkwood.dummy.home> (raw)
Hi,
I have constructed the memory-management developers' homepage
where:
- you can get a link to your mm-related homepage with patches
- with an informative description of all _mm_ patches on your page
- if you don't have a homepage, you can just send the patch +
description to me and I'll put them in the unsorted-patches
section...
In short: this is the place where memory-management patches go,
so people like Jim Pick won't have to deal with them...
Currently this page contains 3 developers' pages (including
my own :), so I also ask for submissions from all memory-
management hackers...
A special mm-wishlist would also be nice... (would it??)
you can get at my page via http://www.fys.ruu.nl/~riel
and (RSN) via Linux-HQ.
Rik.
--
Send Linux memory-management wishes to me: I'm currently looking
for something to hack...
reply other threads:[~1997-12-10 4:04 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.971210044815.5196B-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