From: Michael Kerrisk <mtk.manpages@googlemail.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: man-pages-3.21 is released
Date: Tue, 21 Apr 2009 17:00:56 +1200 [thread overview]
Message-ID: <cfd18e0f0904202200p5544c183j542e1e963b61f146@mail.gmail.com> (raw)
Gidday,
I've released man-pages-3.21.tar.gz - man pages for Linux
This release is now available for download at:
http://www.kernel.org/pub/linux/docs/man-pages
or ftp://ftp.kernel.org/pub/linux/docs/man-pages
man-pages nowadays also has a public git repository at
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
The online changelog is available at
http://www.kernel.org/doc/man-pages/changelog.html
(blogged at
http://linux-man-pages.blogspot.com/2009/04/man-pages-321-is-released.html )
and the current version of the pages is browsable at
http://www.kernel.org/doc/man-pages/
An abridged list of changes that may be of interest to readers of this
list is given below.
Cheers,
Michael
==================== Changes in man-pages-3.21 ====================
New and rewritten pages
-----------------------
pthread_setconcurrency.3
Michael Kerrisk
New page documenting pthread_setconcurrency(3) and
pthread_getconcurrency(3)
pthread_yield.3
Michael Kerrisk
New page documenting pthread_yield(3)
Changes to individual pages
---------------------------
feature_test_macros.7
Michael Kerrisk
Update for glibc 2.10 changes to <features.h>
From glibc 2.10, <features.h> understands the values 200809
for _POSIX_C_SOURCE and 700 for _XOPEN_SOURCE, and makes
corresponding changes to defaults for other feature test macros.
Michael Kerrisk
Add an example program
This example program makes it possible to explore what
feature test macros are set depending on the glibc version
and the macros that are explicitly set.
reply other threads:[~2009-04-21 5: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=cfd18e0f0904202200p5544c183j542e1e963b61f146@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.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;
as well as URLs for NNTP newsgroup(s).