From: Andreas Schwab <schwab@linux-m68k.org>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Cc: Florian Weimer <fweimer@redhat.com>,
Tom Coldrick <thomas.coldrick@codethink.co.uk>
Subject: Re: [PATCH] manual: Avoid name collision in libm ULP table [BZ #28956]
Date: Tue, 05 Apr 2022 17:25:27 +0200 [thread overview]
Message-ID: <87y20jpn6g.fsf@igel.home> (raw)
In-Reply-To: <87mtgzy7ya.fsf@oldenburg.str.redhat.com> (Florian Weimer via Libc-alpha's message of "Tue, 05 Apr 2022 15:29:33 +0200")
On Apr 05 2022, Florian Weimer via Libc-alpha wrote:
> Sorry, why does this say “manual:”? Shouldn't it be ”math:”?
While the file is read by math/gen-libm-test.py, it is only used for
generating the ULPs table in the manual.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2022-04-05 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 9:46 Tom Coldrick
2022-04-05 11:16 ` Adhemerval Zanella
2022-04-11 15:46 ` Carlos O'Donell
2022-04-05 13:29 ` Florian Weimer
2022-04-05 15:25 ` Andreas Schwab [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=87y20jpn6g.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=thomas.coldrick@codethink.co.uk \
/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).