From: "Michael Kerrisk" <mtk-manpages@gmx.net>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: linux-kernel@vger.kernel.org, michael.kerrisk@gmx.net
Subject: Re: man-pages-2.23 is released
Date: Fri, 10 Feb 2006 00:31:18 +0100 (MET) [thread overview]
Message-ID: <10949.1139527878@www004.gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.62.0602091520500.11317@schroedinger.engr.sgi.com>
> > mbind.2
>
> Does this include a description of the new flags MPOL_MF_MOVE and
> MPOL_MF_MOVE_ALL? There is a manpage in Andi Kleen's numactl 0.9.2 that
> describes these.
Not yet, because 2.6.16 (which adds these flags) is not yet
released. However, I have the material in my queue to be
integrated when 2.6.16 is released.
Cheers,
Michael
--
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7
Want to help with man page maintenance?
Grab the latest tarball at
ftp://ftp.win.tue.nl/pub/linux-local/manpages/,
read the HOWTOHELP file and grep the source
files for 'FIXME'.
next prev parent reply other threads:[~2006-02-09 23:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 19:59 man-pages-2.22 " Michael Kerrisk
2006-02-06 22:51 ` Jesse Barnes
2006-02-06 22:59 ` Michael Kerrisk
2006-02-07 0:17 ` Jesse Barnes
2006-02-07 4:40 ` Michael Kerrisk
2006-02-09 23:09 ` man-pages-2.23 " Michael Kerrisk
2006-02-09 23:21 ` Christoph Lameter
2006-02-09 23:31 ` Michael Kerrisk [this message]
2006-02-22 18:15 ` man-pages-2.24 " Michael Kerrisk
2006-03-02 22:00 ` man-pages-2.25 " Michael Kerrisk
2006-03-21 0:48 ` man-pages-2.26 " Michael Kerrisk
2006-03-26 20:05 ` man-pages-2.27 " Michael Kerrisk
2006-03-31 23:44 ` man-pages-2.28 " Michael Kerrisk
2006-04-08 21:07 ` man-pages-2.29 " Michael Kerrisk
2006-05-01 11:04 ` man-pages-2.30 " Michael Kerrisk
2006-05-16 22:10 ` man-pages-2.32 " Michael Kerrisk
2006-05-03 23:27 ` man-pages-2.31 " Michael Kerrisk
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=10949.1139527878@www004.gmx.net \
--to=mtk-manpages@gmx.net \
--cc=clameter@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.kerrisk@gmx.net \
/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®