From: Michael Kerrisk <mtk.manpages@googlemail.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Jim Zemlin <jzemlin@linux-foundation.org>
Subject: man-pages-3.00 is released
Date: Tue, 17 Jun 2008 13:36:04 +0200 [thread overview]
Message-ID: <4857A1A4.7000803@gmail.com> (raw)
Gidday
I've released man-pages-3.00.
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
The change of version number reflects a number of current and planned changes
in man-pages. The most notable recent change is that my work on man-pages is
now supported by a fellowship from the Linux Foundation
(http://linux-man-pages.blogspot.com/2008/06/man-page-is-now-supported.html ).
A full list of the changes in this release can be seen at
http://www.kernel.org/doc/man-pages/changelog.html
(blogged at
http://linux-man-pages.blogspot.com/2008/06/man-pages-300-is-released.html )
The most significant change in this release is that the POSIX man-pages
(Sections 0p, 1p, 3p) are now split out into a separate package, which can be
downloaded here:
http://www.kernel.org/pub/linux/docs/man-pages/man-pages-posix/
The split made sense because the POSIX pages are logically separate from the
Linux man pages. (The POSIX pages are simply copies of text from the
POSIX.1-2003 specification, which we have been granted permission to publish
for Linux. The only kinds of updates these pages see are occasional
formatting fixes, and of course updates when new revisions of the standard
appear, such as the next revision due to appear later this year.)
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
man-pages onlne: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
reply other threads:[~2008-06-17 11:37 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=4857A1A4.7000803@gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=jzemlin@linux-foundation.org \
--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