public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages@googlemail.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: man-pages-2.70 is released
Date: Thu, 06 Dec 2007 10:20:48 +0100	[thread overview]
Message-ID: <4757BEF0.7070909@gmail.com> (raw)

Gidday,

Some news:

* man-pages now has an (irregularly updated) blog:

      http://linux-man-pages.blogspot.com/

* Since man-pages-2.69, each man page now includes a COLOPHON
  section at the end of the page which indicates the version of
  man-pages in which this page is released, and also contains a
  pointer to the man-pages web site.

Repeating some old news:

* man-pages now has a website:

      http://www.kernel.org/doc/man-pages

  The site includes HTML versions of the current set of man-pages.

* The list linux-man@vger.kernel.org has been created for
  the purpose of discussing Linux man page bugs, patches,
  and maintenance.  To subscribe, send a message to
  majordomo@vger.kernel.org, with the body:

        subscribe linux-man

Back to the news as usual...

I recently released man-pages-2.70.

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

    (Note the s/manpages/man-pages/ in these paths;
    a symlink with the old path will exist for
    a limited time.)

Changes in this release consist primarily of formatting and consistency fixes.

Cheers,

Michael
(man-pages maintenance is supported by Google, as a Google engineer 20%
project.)

-- 
Michael Kerrisk
Maintainer of the Linux man-pages project
http://www.kernel.org/doc/man-pages/


                 reply	other threads:[~2007-12-06  9:18 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=4757BEF0.7070909@gmail.com \
    --to=mtk.manpages@googlemail.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