From: Jakub Wilk <jwilk@jwilk.net>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Helge Kreutzmann <debian@helgefjell.de>, <linux-man@vger.kernel.org>
Subject: Re: Errors in man pages, here: expm1.3, bogus full stop
Date: Mon, 6 Jul 2020 13:15:08 +0200 [thread overview]
Message-ID: <20200706111508.vjy5mbttyzd6hy2q@jwilk.net> (raw)
In-Reply-To: <5e2ae325-1998-0a72-9e03-b2a0bd0fe6e2@gmail.com>
* Michael Kerrisk <mtk.manpages@gmail.com>, 2020-07-06, 13:01:
>>Man page: expm1.3
>>Issue: bogus full stop after infinity
>>
>>"Before approximately glibc version 2.11, B<expm1>() raised a bogus invalid "
>>"floating-point exception in addition to the expected overflow exception, and "
>>"returned a NaN instead of positive infinity. for some large positive I<x> "
>>"values,"
>
>This page comes from POSIX. I haven't checked whether the problem was
>in the original source, or introduced during import of the pages.
Wait... How could a note about glibc compatibility come from POSIX?
--
Jakub Wilk
prev parent reply other threads:[~2020-07-06 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 10:12 Errors in man pages, here: expm1.3, bogus full stop Helge Kreutzmann
2020-07-06 11:01 ` Michael Kerrisk (man-pages)
2020-07-06 11:15 ` Jakub Wilk [this message]
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=20200706111508.vjy5mbttyzd6hy2q@jwilk.net \
--to=jwilk@jwilk.net \
--cc=debian@helgefjell.de \
--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 NNTP newsgroup(s).