From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: man-pages-3.75 released
Date: Thu, 16 Oct 2014 11:17:12 +0200 [thread overview]
Message-ID: <543F8D18.1010001@gmail.com> (raw)
Gidday,
The Linux man-pages maintainer proudly announces:
man-pages-3.75 - 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.75
A short summary of the release is blogged at:
http://linux-man-pages.blogspot.com/2014/10/man-pages-375-is-released.html
The current version of the pages is browsable at:
http://man7.org/linux/man-pages/
A few changes in this release that may be of interest to readers of
this list are given below.
Cheers,
Michael
==================== Changes in man-pages-3.75 ====================
Released: 2014-10-15, Düsseldorf
Contributors
------------
The following people contributed patches/fixes or (noted in brackets
in the changelog below) reports, notes, and ideas that have been
incorporated in changes in this release:
Jonny Grant <jg-hus3n9K41k0@public.gmane.org>
Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Robert Schweikert <rjschwei-IBi9RG/b67k@public.gmane.org>
Tetsuo Handa <penguin-kernel-1yMVhJb1mP/7nzcFbJAaVXf5DAMn2ifp@public.gmane.org>
Walter Harms <wharms-fPG8STNUNVg@public.gmane.org>
Apologies if I missed anyone!
New and rewritten pages
-----------------------
pthread_rwlockattr_setkind_np.3
Robert Schweikert [Michael Kerrisk]
New page documenting pthread_rwlockattr_[sg]etkind_np(3)
Documents pthread_rwlockattr_setkind_np(3) and
pthread_rwlockattr_getkind_np(3).
New and changed links
---------------------
pthread_rwlockattr_getkind_np.3
Robert Schweikert
New link to pthread_rwlockattr_setkind_np(3)
Changes to individual pages
---------------------------
readlink.2
Michael Kerrisk [Jonny Grant]
Add free() call to example program
readv.2
Michael Kerrisk
The raw preadv() and pwritev() syscalls split 'offset' into 2 arguments
signal.7
Michael Kerrisk
pthread_mutex_lock() and pthread_cond_wait() are restartable
pthread_mutex_lock(, pthread_cond_wait(), and related APIs are
automatically restarted if interrupted by a signal handler.
unix.7
Michael Kerrisk [Carlos O'Donell, David Miller, Tetsuo Handa]
Various additions and rewordings
Notable changes:
* Clarify some details for pathname sockets.
* Add some advice on portably coding with pathname sockets.
* Note the "buggy" behavior for pathname sockets when
the supplied pathname is 108 bytes (after a report by
Tetsuo Handa).
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2014-10-16 9:17 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=543F8D18.1010001@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.