From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: Linux MM <linux-mm@kvack.org>
Subject: priorities for 2.2
Date: Mon, 21 Sep 1998 21:16:24 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.3.96.980921211300.26074D-100000@mirkwood.dummy.home> (raw)
Hi,
I'm wondering, what exactly _are_ our priorities for 2.2?
Apart from documentation, what else needs fixing and/or
tuning before 2.2 is out, who's working on what and which
jobs are left undone?
I know I'll be working on the documentation (HTMLizing
the Documentation/sysctl/* and writing a bit more) but
I can sure use some help...
I'm sure there are also other important things that need
help and even things that aren't done. Maybe it's time to
put our 2.3 projects aside for a while and focus on the
last bits of 2.2 readyness...
Rik.
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
reply other threads:[~1998-09-21 22:01 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.96.980921211300.26074D-100000@mirkwood.dummy.home \
--to=h.h.vanriel@phys.uu.nl \
--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