From: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
To: Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
List util-linux-ng
<util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Sukadev Bhattiprolu
<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org,
sukadev-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
Subject: Re: [RFC] devpts man page update
Date: Mon, 01 Dec 2008 14:41:51 -0800 [thread overview]
Message-ID: <4934682F.7050305@zytor.com> (raw)
In-Reply-To: <20081201223913.GF2956-sHeGUpI7y9L/9pzu0YdTqQ@public.gmane.org>
Karel Zak wrote:
>
>> 1. Agree that this is the way to do it.
>> 2. Add the options to section 4.
>> 3. Clean up mount(8).
>
> 4. found a way how maintain and keep the man pages up to date.
>
As far as 4. is concerned -- I personally think that keeping man pages
that directly describe kernel interfaces (e.g. section 2, and parts of
4, 5, and 7) in the kernel git tree is the most logical option.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-12-01 22:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 18:17 [RFC] devpts man page update Sukadev Bhattiprolu
[not found] ` <20081126181732.GA1509-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-11-27 11:38 ` Michael Kerrisk
[not found] ` <cfd18e0f0811270338o392daf81kdfd46cec51325891-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-27 19:14 ` H. Peter Anvin
2008-12-01 18:10 ` Sukadev Bhattiprolu
[not found] ` <20081201181055.GA12493-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-12-01 19:31 ` Michael Kerrisk
[not found] ` <cfd18e0f0812011131g2bbe2d6flb8cc89eaa7f96ad4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-12-01 19:42 ` H. Peter Anvin
[not found] ` <49343E32.50707-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2008-12-01 20:05 ` Michael Kerrisk
[not found] ` <cfd18e0f0812011205w62f30725m53f4b16cea3272aa-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-12-01 21:08 ` Andries E. Brouwer
2008-12-01 21:35 ` H. Peter Anvin
2008-12-01 22:39 ` Karel Zak
[not found] ` <20081201223913.GF2956-sHeGUpI7y9L/9pzu0YdTqQ@public.gmane.org>
2008-12-01 22:41 ` H. Peter Anvin [this message]
[not found] ` <4934682F.7050305-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2008-12-01 23:00 ` Karel Zak
[not found] ` <20081201230031.GA26838-sHeGUpI7y9L/9pzu0YdTqQ@public.gmane.org>
2008-12-01 23:03 ` H. Peter Anvin
2008-12-01 23:19 ` H. Peter Anvin
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=4934682F.7050305@zytor.com \
--to=hpa-ymnouzjc4hwavxtiumwx3w@public.gmane.org \
--cc=alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org \
--cc=kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=sukadev-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.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