From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Michael Kerrisk" <mtk-manpages@gmx.net>
Cc: linux-kernel@vger.kernel.org, michael.kerrisk@gmx.net,
Andries.Brouwer@cwi.nl
Subject: Re: man-pages-2.08 is released
Date: Wed, 12 Oct 2005 10:10:15 -0700 [thread overview]
Message-ID: <200510121010.16274.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <30041.1129134415@www32.gmx.net>
On Wednesday, October 12, 2005 9:26 am, Michael Kerrisk wrote:
> 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):
Would it make sense for some of the man pages (or maybe all of them) that
correspond directly to kernel interfaces (e.g. syscalls, procfs & sysfs
descriptions) to be bundled directly with the kernel? Andrew is
generally pretty good about asking people to update the stuff in
Documentation/ when necessary, so maybe the man pages would be kept more
up to date if developers were forced to deal with them more directly.
OTOH, they comprise a fairly large package, so adding them to the kernel
tarball would increase its size a lot.
The man pages are great; I'm just thinking that if some of them were
bundled with the kernel there'd be a bit less work for you to do (just
proofreading and acking changes hopefully). Also, if they were there,
it might motivate people to convert some of the stuff in Documentation
to section 7 man pages (the janitors have been doing a lot of good
stuff, maybe that would be another area where they could contribute).
Thanks,
Jesse
next prev parent reply other threads:[~2005-10-12 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <434D5224.9754.10AC691@localhost>
2005-10-12 16:26 ` Michael Kerrisk
2005-10-12 17:10 ` Jesse Barnes [this message]
2005-10-13 8:52 ` Michael Kerrisk
2005-10-13 17:46 ` Jesse Barnes
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=200510121010.16274.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.kerrisk@gmx.net \
--cc=mtk-manpages@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®