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.63 is released
Date: Tue, 18 Mar 2014 17:52:16 +0100 [thread overview]
Message-ID: <532879C0.7080507@gmail.com> (raw)
Gidday,
The Linux man-pages maintainer proudly announces:
man-pages-3.63 - man pages for Linux
He also proudly announces that man-pages recently passed
10,000 commits since he took over as maintainer in 2004
(https://plus.google.com/u/0/+MichaelKerrisk/posts/SVH47FGnQCN ).
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.63
A short summary of the release is blogged at:
http://linux-man-pages.blogspot.com/2014/03/man-pages-363-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.63 ====================
Released: 2014-03-18, Munich
New and rewritten pages
-----------------------
duplocale.3
Michael Kerrisk
New page documenting duplocale(3)
newlocale.3
Michael Kerrisk [Mike Frysinger]
New page documenting newlocale(3) and freelocale(3)
uselocale.3
Michael Kerrisk
New page documenting uselocale(3)
Newly documented interfaces in existing pages
---------------------------------------------
open.2
Michael Kerrisk
Document O_DSYNC and rewrite discussion of O_SYNC
proc.5
Michael Kerrisk
Document /proc/sys/kernel/random/uuid
locale.7
Michael Kerrisk
Document LC_ADDRESS
Document LC_IDENTIFICATION
Document LC_MEASUREMENT
Document LC_NAME
Document LC_PAPER
Document LC_TELEPHONE
Changes to individual pages
---------------------------
readahead.2
Phillip Susi [Corrado Zoccolo, Gregory P. Smith, Zhu Yanhai, Michael Kerrisk, Christoph Hellwig]
Don't claim the call blocks until all data has been read
The readahead(2) man page was claiming that the call blocks until
all data has been read into the cache. This is incorrect.
See https://bugzilla.kernel.org/show_bug.cgi?id=54271
fts.3
Christoph Hellwig [Michael Kerrisk]
The fts(3) API does not work with LFS builds
As pointed out during a recent discussion on libc-hacker the
fts(3) APIs can't be used with large file offsets:
https://sourceware.org/bugzilla/show_bug.cgi?id=15838
core.5
Mike Frysinger [Michael Kerrisk]
Document core_pattern %d specifier
Document %P core_pattern specifier
--
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:[~2014-03-18 16:52 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=532879C0.7080507@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 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.