From: Jeff Moyer <jmoyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: Cyril Hrubis <chrubis-AlSwsSmVLrQ@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: aio manuals
Date: Mon, 07 May 2012 17:21:29 -0400 [thread overview]
Message-ID: <x49havrsn52.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <CAKgNAkjZS0VyV4y6P-NyrLv8_a8G2K6=yFPijef3d3wfQuPwXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (Michael Kerrisk's message of "Tue, 8 May 2012 09:14:23 +1200")
"Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Here's what I think should be done:
>
> 1) For io_submit, io_cancel, io_getevents, io_destroy, io_setup:
>
> a) There should be .2 pages provided by man-pages that document the
> raw system calls. These pages need a bit of cleaning up. These pages
> should be updated to focus on the system calls, and note the existence
> of libaio and the existence of the wrappers it provides.
>
> b) There should be .3 pages provided by libaio. (The pages should be
> provided by libaio, because that's the library that implements them.
> If those wrappers were in glibc, then I'd have said that man-pages
> should provide them.) Since the wrappers are mostly very thin, I think
> it would be sufficient to have very short man pages that:
> - note the need to link with "-laio"
> - document io_context_t versus aio_context_t
> - refer the reader to the corresponding .2 page for details of behavior.
>
> 2) For the other io_* functions provided by libaio:
>
> a) libaio should provide man pages. (And this seems already to be the case.)
>
> 3) For the aio_* and lio_listio functions:
>
> a) The right place to document these is man-pages, since they are
> glibc interfaces, not libaio interfaces. man-pages already has such
> pages.
>
> b) The versions of these man pages in libaio should be dropped. The
> pages seem to be unmaintained, and they describe interfaces that are
> not even part of libaio. Along the way, we should check if there are
> pieces in the libaio pages that could usefully be added to the
> corresponding man-pages pages.
>
> How does the above sound?
Sounds like a plan. I'll clean this up in the coming weeks, if nobody
beats me to it.
Cheers,
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-man" 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:[~2012-05-07 21:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 18:06 aio manuals Cyril Hrubis
[not found] ` <20110309180600.GA14533-n1fJoQsqRnsVI8jrpt9EEQ@public.gmane.org>
2011-03-09 17:53 ` Jeff Moyer
[not found] ` <x49ei6gnpsx.fsf-RRHT56Q3PSP4kTEheFKJxxDDeQx5vsVwAInAS/Ez/D0@public.gmane.org>
2011-03-16 10:43 ` Cyril Hrubis
[not found] ` <20110316104356.GB32095-n1fJoQsqRnsVI8jrpt9EEQ@public.gmane.org>
2011-03-16 14:26 ` Jeff Moyer
[not found] ` <x49pqpr9m5l.fsf-RRHT56Q3PSP4kTEheFKJxxDDeQx5vsVwAInAS/Ez/D0@public.gmane.org>
2011-03-16 15:20 ` Cyril Hrubis
[not found] ` <20110316152018.GG2096-n1fJoQsqRnsVI8jrpt9EEQ@public.gmane.org>
2011-10-13 8:29 ` Cyril Hrubis
[not found] ` <20111013082918.GA17800-n1fJoQsqRnsVI8jrpt9EEQ@public.gmane.org>
2011-10-17 19:53 ` Jeff Moyer
2012-05-05 12:26 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkj68CwJFkqYNvz5X5Jt+6xTwVb1eR+vSkXmFYorQvHJ5A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-05-07 13:44 ` Jeff Moyer
[not found] ` <x4962c8t8b8.fsf-RRHT56Q3PSP4kTEheFKJxxDDeQx5vsVwAInAS/Ez/D0@public.gmane.org>
2012-05-07 20:40 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkh9jnybota9W_-iD6Uc6c2pJuMiTus2GLk53ysvCVhhRQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-05-07 20:52 ` Jeff Moyer
2012-05-07 21:14 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkjZS0VyV4y6P-NyrLv8_a8G2K6=yFPijef3d3wfQuPwXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-05-07 21:21 ` Jeff Moyer [this message]
2012-05-09 14:27 ` Cyril Hrubis
[not found] ` <20120509142713.GA7912-n1fJoQsqRnsVI8jrpt9EEQ@public.gmane.org>
2012-05-09 23:59 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkjki3nY8awPZ7tSd6D=xErF9J7D_S_QaeKpXHVq4YL+_Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-11-11 8:12 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkg5ukEk_jzH3fouT9pe=HJnV+OhjOL1BzRzxviz67pAgA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-11-12 10:04 ` chrubis-AlSwsSmVLrQ
[not found] ` <20121112100446.GA6764-J5syqNJeCN7twjQa/ONI9g@public.gmane.org>
2012-11-12 14:26 ` Jeff Moyer
[not found] ` <x49vcdakid2.fsf-RRHT56Q3PSP4kTEheFKJxxDDeQx5vsVwAInAS/Ez/D0@public.gmane.org>
2012-11-12 16:09 ` chrubis-AlSwsSmVLrQ
[not found] ` <20121112160937.GA23439-J5syqNJeCN7twjQa/ONI9g@public.gmane.org>
2013-02-25 8:07 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkiG3psL_7A74UV2sLKkCYfMZjts+wCFWdkKbaAO_W2Wuw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-27 11:48 ` chrubis-AlSwsSmVLrQ
2013-02-27 13:02 ` Jeff Moyer
2013-04-16 6:34 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkg0TjfQpyrJtZc63vTH_NPqe2LTMFYrP1ABLCXtx_f4Wg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-16 10:27 ` chrubis-AlSwsSmVLrQ
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=x49havrsn52.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=chrubis-AlSwsSmVLrQ@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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;
as well as URLs for NNTP newsgroup(s).