From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: mtk.manpages@gmail.com
Subject: man-pages-3.81 is released
Date: Mon, 02 Mar 2015 17:41:20 +0100 [thread overview]
Message-ID: <54F492B0.3040609@gmail.com> (raw)
Gidday,
The Linux man-pages maintainer proudly announces:
man-pages-3.81 - man pages for Linux
Tarball download:
http://www.kernel.org/doc/man-pages/download.html
Git repository:
https://git.kernel.org/cgit/docs/man-pages/man-pages.git/
Online changelog:
http://man7.org/linux/man-pages/changelog.html#release_3.81
A short summary of the release is blogged at:
http://linux-man-pages.blogspot.com/2015/03/man-pages-381-is-released.html
===
The changes in man-pages-3.81 relate exclusively to the (glibc)
thread-safety markings in various man pages. More than 400 patches,
mainly by Ma Shimiao and Peng Haitao of Fujitsu brought the following
changes:
* Thread-safety information has been added to many more pages.
* The thread-safety notation in man-pages has been made consistent
with the notation used in the GNU C Library Manual.
* Thread-safety information in man-pages has been checked for
consistency with the same information in the GNU C Library Manual.
In some cases these, this has resulted in refinements to the
markings in man-pages.
* The thread-safety information in man-pages has been been converted
from a plain text layout to a tabular layout, for ease of reading.
By now, thanks mainly to the work of Peng Haitao and Ma Shimiao,
nearly 400 of the (around 980) pages in man-pages carry thread-safety
information.
In addition, a new attributes(7) man page, based on text supplied
by Alexandre Oliva (who was responsible for adding thread-safety
information to the GNU C Library manual) provides an overview of the
thread-safety concepts documented in man-pages, and a description of
the notation used in man-pages to describe the thread safety of
functions. (Thanks also to Carlos O'Donell for helping us to obtain
the permissions needed so that man-pages could recycle this text
from the GNU C Library manual.).
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
reply other threads:[~2015-03-02 16:41 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=54F492B0.3040609@gmail.com \
--to=mtk.manpages@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).