From: Paul Jackson <pj@sgi.com>
To: Ray Bryant <raybry@sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: manual page migration -- issues
Date: Tue, 15 Feb 2005 15:11:21 -0800 [thread overview]
Message-ID: <20050215151121.48ca91d7.pj@sgi.com> (raw)
In-Reply-To: <42127C38.9000406@sgi.com>
Ray - could you repost your excellent re-introduction to linux-mm, with
the specific email addresses of those who have shown an interest so far
on lkml? Many of us treat email to "a list plus ourselves" differently
than we treat email just to "a list".
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373, 1.925.600.0401
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-02-15 23:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 22:48 manual page migration -- issues Ray Bryant
2005-02-15 23:11 ` Paul Jackson [this message]
2005-02-15 23:26 ` Ray Bryant
2005-02-15 23:29 ` Dave Hansen
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=20050215151121.48ca91d7.pj@sgi.com \
--to=pj@sgi.com \
--cc=linux-mm@kvack.org \
--cc=raybry@sgi.com \
/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