From: Alejandro Colomar via Libc-alpha <libc-alpha@sourceware.org>
To: mtk.manpages@gmail.com
Cc: Alejandro Colomar <colomar.6.4.3@gmail.com>,
linux-man@vger.kernel.org, libc-alpha@sourceware.org
Subject: [PATCH 2/3] system_data_types.7: Add 'clock_t'
Date: Sat, 17 Oct 2020 23:37:58 +0200 [thread overview]
Message-ID: <20201017213758.9270-2-colomar.6.4.3@gmail.com> (raw)
In-Reply-To: <20201017213758.9270-1-colomar.6.4.3@gmail.com>
Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
---
Hi Michael,
Does that dash (in "real-floating") need to be escaped?
In my terminal I see it correctly,
but I've seen you escaping some of them and don't know the reason why.
Should they be escaped always, or is it only sometimes, and when?
Thanks,
Alex
man7/system_data_types.7 | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/man7/system_data_types.7 b/man7/system_data_types.7
index dc5f65c0d..6a1442ccd 100644
--- a/man7/system_data_types.7
+++ b/man7/system_data_types.7
@@ -85,6 +85,28 @@ See also:
.BR aio_write (3),
.BR lio_listio (3)
.RE
+.\"------------------------------------- clock_t ----------------------/
+.TP
+.I clock_t
+.RS
+Include:
+.I <time.h>
+or
+.IR <sys/types.h> .
+Alternatively,
+.IR <sys/time.h> .
+.PP
+Used for system time in clock ticks.
+According to POSIX,
+it shall be an integer type or a real-floating type.
+.PP
+Conforming to:
+C99 and later; POSIX.1-2001 and later.
+.PP
+See also:
+.BR times (2),
+.BR clock (3)
+.RE
.\"------------------------------------- div_t ------------------------/
.TP
.I div_t
--
2.28.0
next prev parent reply other threads:[~2020-10-17 21:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 21:37 [PATCH 1/3] system_data_types.7: time_t: Add Versions note Alejandro Colomar via Libc-alpha
2020-10-17 21:37 ` Alejandro Colomar via Libc-alpha [this message]
2020-10-18 5:56 ` [PATCH 2/3] system_data_types.7: Add 'clock_t' Michael Kerrisk (man-pages) via Libc-alpha
2020-10-18 9:10 ` Alejandro Colomar via Libc-alpha
2020-10-18 13:09 ` Michael Kerrisk (man-pages) via Libc-alpha
2020-10-19 17:40 ` \- vs - (Was [Re: [PATCH 2/3] system_data_types.7: Add 'clock_t']) Alejandro Colomar via Libc-alpha
2020-10-17 21:37 ` [PATCH 3/3] clock_t.3: New link to system_data_types(3) Alejandro Colomar via Libc-alpha
2020-10-18 16:52 ` Michael Kerrisk (man-pages) via Libc-alpha
2020-10-18 1:05 ` [PATCH 1/3] system_data_types.7: time_t: Add Versions note Paul Eggert
2020-10-18 2:32 ` Zack Weinberg
2020-10-18 5:46 ` Michael Kerrisk (man-pages) via Libc-alpha
2020-10-18 9:02 ` Alejandro Colomar via Libc-alpha
2020-10-18 13:05 ` Michael Kerrisk (man-pages) via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201017213758.9270-2-colomar.6.4.3@gmail.com \
--to=libc-alpha@sourceware.org \
--cc=colomar.6.4.3@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).