mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael Kerrisk" <mtk-manpages@gmx.net>
To: linux-kernel@vger.kernel.org
Cc: michael.kerrisk@gmx.net
Subject: man-pages-2.22 is released
Date: Mon, 6 Feb 2006 20:59:46 +0100 (MET)	[thread overview]
Message-ID: <16806.1139255986@www031.gmx.net> (raw)

Gidday,

I recently released man-pages-2.22, which contains 
sections 2, 3, 4, 5, and 7 of the manual pages.  These 
sections describe the following:

2: (Linux) system calls
3: (libc) library functions
4: Devices
5: File formats and protocols
7: Overview pages, conventions, etc.

As far as this list is concerned the most relevant parts are: 
all of sections 2 and 4, which describe kernel-userland interfaces; 
in section 5, the proc(5) manual page, which attempts (it's always 
catching up) to be a comprehensive description of /proc; and 
various pages in section 7, some of which are overview pages of 
kernel features (e.g., networking protocols).

This is a request to kernel developers: if you make a change 
to a kernel-userland interface, or observe a discrepancy 
between the manual pages and reality, would you please send 
me (at mtk-manpages@gmx.net ) one of the following 
(in decreasing order of preference):

1. An in-line "diff -u" patch with text changes for the 
   corresponding manual page.  (The most up-to-date version 
   of the manual pages can always be found at
   ftp://ftp.win.tue.nl/pub/linux-local/manpages or
   ftp://ftp.kernel.org/pub/linux/docs/manpages .)

2. An email describing the changes, which I can then 
   integrate into the appropriate manual page.

3. A message alerting me that some part of the manual pages 
   does not correspond to reality.  Eventually, I will try to 
   remedy the situation.

Obviously, as we get further down this list, more of my time 
is required, and things may go slower, especially when the
changes concern some part of the kernel that I am ignorant 
about and I can't find someone to assist.

Cheers,

Michael

-- 
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
ftp://ftp.win.tue.nl/pub/linux-local/manpages/, 
read the HOWTOHELP file and grep the source 
files for 'FIXME'.

             reply	other threads:[~2006-02-06 19:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 19:59 Michael Kerrisk [this message]
2006-02-06 22:51 ` Jesse Barnes
2006-02-06 22:59   ` Michael Kerrisk
2006-02-07  0:17     ` Jesse Barnes
2006-02-07  4:40       ` Michael Kerrisk
2006-02-09 23:09 ` man-pages-2.23 " Michael Kerrisk
2006-02-09 23:21   ` Christoph Lameter
2006-02-09 23:31     ` Michael Kerrisk
2006-02-22 18:15   ` man-pages-2.24 " Michael Kerrisk
2006-03-02 22:00     ` man-pages-2.25 " Michael Kerrisk
2006-03-21  0:48       ` man-pages-2.26 " Michael Kerrisk
2006-03-26 20:05         ` man-pages-2.27 " Michael Kerrisk
2006-03-31 23:44           ` man-pages-2.28 " Michael Kerrisk
2006-04-08 21:07           ` man-pages-2.29 " Michael Kerrisk
2006-05-01 11:04             ` man-pages-2.30 " Michael Kerrisk
2006-05-16 22:10               ` man-pages-2.32 " Michael Kerrisk
2006-05-03 23:27       ` man-pages-2.31 " Michael Kerrisk

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=16806.1139255986@www031.gmx.net \
    --to=mtk-manpages@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.kerrisk@gmx.net \
    /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

all inboxes | Powered by JetHome®