From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Michael Kerrisk" <mtk-manpages@gmx.net>
Cc: linux-kernel@vger.kernel.org, michael.kerrisk@gmx.net
Subject: Re: man-pages-2.22 is released
Date: Mon, 6 Feb 2006 16:17:12 -0800 [thread overview]
Message-ID: <200602061617.12713.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <28306.1139266765@www031.gmx.net>
On Monday, February 6, 2006 2:59 pm, Michael Kerrisk wrote:
> > Wouldn't it be easier for you to keep them up to date if sections 2,
> > 4, and parts of 5 were included in the kernel source tree?
> > Documentation updates could be enforced as part of the patch
> > process--all you'd have to do is NAK patches that modified userland
> > interfaces if they didn't contain documentation updates (and I'm
> > sure others would help you with that task).
>
> Life is not so simple, as I think we discussed when you made
> a similar comment after my man-pages-2.08 release. Maybe the
> system can be improved still. Currently Andrew Morton is being
> rather good about CCing me on patches that are likely to need
> man-pages changes. (Thanks Andrew!)
Yeah, vigilance is key; maybe I'm wrong that putting the kernel stuff
into the kernel tree would help, but it's worth a try, don't you
think? :)
> > Likewise with the glibc stuff. Doesn't it belong with the glibc
> > project? Wouldn't that make more sense, both from a packaging and
> > maintenance perspective?
>
> Not really -- glibc has a differnt philosophy about documentation
> (less focus on historical information and less comparison
> with other Unix systems, as far as I can see), and uses info(1),
> not man(1).
Oh yeah, forgot about that... I guess man vs. info and glibc development
philosophy is for another thread.
Thanks,
Jesse
next prev parent reply other threads:[~2006-02-07 0:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 19:59 Michael Kerrisk
2006-02-06 22:51 ` Jesse Barnes
2006-02-06 22:59 ` Michael Kerrisk
2006-02-07 0:17 ` Jesse Barnes [this message]
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=200602061617.12713.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--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
Powered by JetHome