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@vger.kernel.org
Subject: Re: [PATCH v2 1/2] system_data_types.7: Add 'fexcept_t'
Date: Wed, 23 Sep 2020 15:31:27 +0200 [thread overview]
Message-ID: <173479d9-2bb5-81da-cfff-cb4192e9d675@gmail.com> (raw)
In-Reply-To: <20200923131706.21393-1-colomar.6.4.3@gmail.com>
Hi Alex,
On 9/23/20 3:17 PM, Alejandro Colomar wrote:
> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
> ---
>
> Hi Michael,
>
> On 2020-09-23 10:36, Michael Kerrisk (man-pages) wrote:
>> [Thorsten, I have removed you from the CC because I get persistent
>> bounce messages whenever I send you mail. Hopefully you see this reply
>> via the list.]
>
> Me too :(
>
>> While I'm pretty sure they would allow this without problem, I'm
>> wondering if it's worth the effort. Ideally, we'd have text written by
>> someone in their own words. Reproducing the text of the standard has
>> limited value, since people can in any case consult the standard
>> directly.
>>
>> Alex, how about we just go much simpler, saying something like:
>>
>> [[
>> This type represents floating-point status flags; for further details
>> see fenv(3).
>> ]]
>
> Nice and simple.
>
> Thanks,
>
> Alex
Thanks! Patch applied.
Cheers,
Michael
> man7/system_data_types.7 | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/man7/system_data_types.7 b/man7/system_data_types.7
> index 4352d6a6e..ea3e25175 100644
> --- a/man7/system_data_types.7
> +++ b/man7/system_data_types.7
> @@ -110,7 +110,22 @@ Conforming to: C99 and later; POSIX.1-2001 and later.
> .IP
> See also:
> .BR fenv (3)
> -.\"------------------------------------- gid_t ----------------------/
> +.\"------------------------------------- fexcept_t --------------------/
> +.TP
> +.I fexcept_t
> +.IP
> +Include:
> +.IR <fenv.h> .
> +.IP
> +This type represents the floating-point status flags collectively;
> +for further details see
> +.BR fenv (3).
> +.IP
> +Conforming to: C99 and later; POSIX.1-2001 and later.
> +.IP
> +See also:
> +.BR fenv (3)
> +.\"------------------------------------- gid_t ------------------------/
> .TP
> .I gid_t
> .IP
>
--
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-23 13:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 15:38 [PATCH 1/2] system_data_types.7: Add 'fexcept_t' Alejandro Colomar
2020-09-22 15:38 ` [PATCH 2/2] fexcept_t.3: New link to system_data_types(7) Alejandro Colomar
2020-09-23 13:17 ` [PATCH v2 1/2] system_data_types.7: Add 'fexcept_t' Alejandro Colomar
2020-09-23 13:31 ` Michael Kerrisk (man-pages) [this message]
2020-09-23 13:17 ` [PATCH v2 2/2] fexcept_t.3: New link to system_data_types(7) Alejandro Colomar
2020-09-23 13:31 ` Michael Kerrisk (man-pages)
2020-09-22 19:57 ` [PATCH 1/2] system_data_types.7: Add 'fexcept_t' Michael Kerrisk (man-pages)
2020-09-22 20:05 ` Alejandro Colomar
2020-09-22 20:14 ` Michael Kerrisk (man-pages)
2020-09-22 20:32 ` Alejandro Colomar
2020-09-22 20:37 ` Michael Kerrisk (man-pages)
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=173479d9-2bb5-81da-cfff-cb4192e9d675@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=colomar.6.4.3@gmail.com \
--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