From: Michael Kerrisk <mtk-manpages@gmx.net>
To: lkml <linux-kernel@vger.kernel.org>
Subject: man-pages-2.54 is released
Date: Fri, 08 Jun 2007 14:50:29 +0200 [thread overview]
Message-ID: <46695095.2020503@gmx.net> (raw)
Gidday,
I just released man-pages-2.54
This release is now available for download at:
http://www.kernel.org/pub/linux/docs/manpages
or ftp://ftp.kernel.org/pub/linux/docs/manpages
or mirrors: ftp://ftp.XX.kernel.org/pub/linux/docs/manpages
and soon at:
ftp://ftp.win.tue.nl/pub/linux-local/manpages
This release includes a new page, man-pages.7, that describes the
conventions that should be used when writing pages for man-pages. A few
other changes that may be of interest to readers of this list are are noted
below.
Cheers,
Michael
==================== Changes in man-pages-2.54 ====================
New pages
---------
man-pages.7
mtk
A description of the conventions that should be followed
when writing pages for the man-pages package.
Changes to individual pages
---------------------------
fcntl.2
mtk
Remove misleading text about setting O_ASYNC when calling
open(); one must use fcntl() F_SETFL for this task.
fdatasync.2
mtk
Converted outdated BUGS note about fdatasync() being
equivalent to fsync() on Linux 2.2 into a NOTES note
about this historical behaviour.
mprotect.2
mtk, after an observation by Emmanuel Mogenet
A much improved example program.
mtk
Significant rewrites and additions to description.
--
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
http://www.kernel.org/pub/linux/docs/manpages/
read the HOWTOHELP file and grep the source files for 'FIXME'.
next reply other threads:[~2007-06-08 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 12:50 Michael Kerrisk [this message]
2007-06-08 14:02 ` man-pages-2.54 is released Gerhard Mack
2007-06-08 16:03 ` Michael Kerrisk
2007-06-08 18:45 ` Jan Engelhardt
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=46695095.2020503@gmx.net \
--to=mtk-manpages@gmx.net \
--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.