From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man <linux-man@vger.kernel.org>,
Florian Weimer <fweimer@redhat.com>,
libbsd@lists.freedesktop.org
Subject: Re: [RFC v1] system_data_types.7: Draft (and links to it: <type>.3)
Date: Mon, 14 Sep 2020 12:55:17 +0200 [thread overview]
Message-ID: <a160fb7e-2f72-9532-ada5-9978a994d3bd@gmail.com> (raw)
In-Reply-To: <23bfb4c9-9cab-8d1f-46a2-00932501b5b8@gmail.com>
Hi Alex,
On 9/14/20 12:37 PM, Michael Kerrisk (man-pages) wrote:
> Hello Alex,
>
> On 9/14/20 2:20 AM, Alejandro Colomar wrote:
> I'm going to hold my finger in the wind, and say: lets restrict the
> list to what seem like the most relevant APIs, where obviously that is
> a somewhat subjective choice. You could include all the other APIs in
> .\" comments, so we can see what's excluded, and this may trigger some
> tweaking. So, for 'struct timespec' the list might be as simple as:
>
> clock_gettime(2), clock_nanosleep(2), nanosleep(2)
> timerfd_gettime(2), timer_gettime(2)
Just to add to this. Even if limiting to "relevant" APIs,
I think some of the lists might still be quite long (which
is okay). For example, I do expect the 'time_t' list will
remain long.
Some of your items in the 'timer_t' list definitely don't
belong (timer_getoverrun, timer_delete).
The 'sigval' list looks about right.
I think the 'timeval' list could be trimmed back a bit.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-09-14 10:55 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 12:47 [IDEA] New pages for types: structs and typedfefs Alejandro Colomar
2020-09-12 6:33 ` Michael Kerrisk (man-pages)
2020-09-12 8:59 ` Alejandro Colomar
2020-09-12 9:26 ` Alejandro Colomar
2020-09-13 12:01 ` Michael Kerrisk (man-pages)
2020-09-13 12:53 ` Alejandro Colomar
2020-09-13 20:20 ` Michael Kerrisk (man-pages)
2020-09-13 21:29 ` Alejandro Colomar
2020-09-14 0:20 ` [RFC v1] system_data_types.7: Draft (and links to it: <type>.3) Alejandro Colomar
2020-09-14 10:37 ` Michael Kerrisk (man-pages)
2020-09-14 10:55 ` Michael Kerrisk (man-pages) [this message]
2020-09-22 20:21 ` [IDEA] New pages for types: structs and typedfefs Michael Kerrisk (man-pages)
2020-09-22 20:38 ` Thorsten Glaser
2020-09-23 8:36 ` Michael Kerrisk (man-pages)
2020-09-23 19:54 ` Thorsten Glaser
2020-09-14 9:19 ` Jakub Wilk
2020-09-14 9:49 ` Alejandro Colomar
2020-09-18 2:16 ` Guillem Jover
2020-09-19 8:45 ` Michael Kerrisk (man-pages)
2020-09-14 10:22 ` Alejandro Colomar
2020-09-14 14:03 ` [RFC v2] system_data_types.7: Draft v2 Alejandro Colomar
2020-09-14 15:00 ` Michael Kerrisk (man-pages)
2020-09-14 15:52 ` Alejandro Colomar
2020-09-14 19:33 ` Michael Kerrisk (man-pages)
2020-09-15 0:47 ` [RFC v3] sigval.3, ssize_t.3, suseconds_t.3, time_t.3, timer_t.3, timespec.3, timeval.3, system_data_types.7: Document system types (draft v3) Alejandro Colomar
2020-09-15 6:22 ` Michael Kerrisk (man-pages)
2020-09-15 13:33 ` [RFC v4] system_data_types.7: Document sigval, ssize_t, suseconds_t, time_t, timer_t, timespec & timeval Alejandro Colomar
2020-09-15 21:30 ` Michael Kerrisk (man-pages)
2020-09-16 0:59 ` Thorsten Glaser
2020-09-16 8:03 ` Michael Kerrisk (man-pages)
2020-09-16 10:06 ` Andries E. Brouwer
2020-09-16 11:00 ` Michael Kerrisk (man-pages)
2020-09-16 10:52 ` [RFC v5] system_data_types.7: Document types: sigval, ssize_t, suseconds_t, time_t, timer_t, timespec, timeval Alejandro Colomar
2020-09-16 10:56 ` Alejandro Colomar
2020-09-16 11:01 ` [RFC v6] " Alejandro Colomar
2020-09-16 19:24 ` Michael Kerrisk (man-pages)
2020-09-16 19:51 ` Alejandro Colomar
2020-09-16 21:32 ` Thorsten Glaser
2020-09-17 9:23 ` Alejandro Colomar
2020-09-17 10:27 ` Michael Kerrisk (man-pages)
2020-09-17 10:42 ` [PATCH v7 0/8] Document system data types Alejandro Colomar
2020-09-17 21:05 ` Michael Kerrisk (man-pages)
2020-09-17 21:16 ` Alejandro Colomar
2020-09-17 10:42 ` [PATCH v7 1/8] system_data_types.7: Document types: sigval, ssize_t, suseconds_t, time_t, timer_t, timespec, timeval Alejandro Colomar
2020-09-17 10:43 ` [PATCH v7 2/8] sigval.3: Add link page Alejandro Colomar
2020-09-17 10:43 ` [PATCH v7 3/8] ssize_t.3: " Alejandro Colomar
2020-09-17 10:43 ` [PATCH v7 4/8] suseconds_t.3: " Alejandro Colomar
2020-09-17 10:43 ` [PATCH v7 5/8] time_t.3: " Alejandro Colomar
2020-09-17 10:43 ` [PATCH v7 6/8] timer_t.3: " Alejandro Colomar
2020-09-17 10:43 ` [PATCH v7 7/8] timespec.3: " Alejandro Colomar
2020-09-17 10:43 ` [PATCH v7 8/8] timeval.3: " Alejandro Colomar
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=a160fb7e-2f72-9532-ada5-9978a994d3bd@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=colomar.6.4.3@gmail.com \
--cc=fweimer@redhat.com \
--cc=libbsd@lists.freedesktop.org \
--cc=linux-man@vger.kernel.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