From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: linux-kernel@vger.kernel.org, akpm@osdl.org, arjan@infradead.org
Subject: [PATCH 0/4] pmap
Date: Sun, 22 Jan 2006 17:15:24 -0500 (EST) [thread overview]
Message-ID: <200601222215.k0MMFOYD213932@saturn.cs.uml.edu> (raw)
0 index (this message)
1 add /proc/*/pmap files
2 remove /proc/*/smaps files (depends on #1)
3 fix integer overflow (depends on #2)
4 fix permissions (depends on #2)
I found an old email account that still supports adding raw binay data
to an email message body. I really wish we could get away from this,
because it makes contributions damn near impossible for some people.
Other people are far worse off than I am.
These all apply to -git4, grabbed Saturday night.
next reply other threads:[~2006-01-22 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-22 22:15 Albert D. Cahalan [this message]
2006-01-22 22:52 ` Jesper Juhl
2006-01-22 23:34 ` Randy.Dunlap
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=200601222215.k0MMFOYD213932@saturn.cs.uml.edu \
--to=acahalan@cs.uml.edu \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®