From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] regenerate ulps for x86_64 after cf7ffdd
Date: Tue, 14 Feb 2023 10:55:01 +0100 [thread overview]
Message-ID: <mwfsb81si2.fsf@coriandre.loria.fr> (raw)
In-Reply-To: <87o7pwa89s.fsf@oldenburg.str.redhat.com> (message from Florian Weimer on Tue, 14 Feb 2023 10:47:11 +0100)
Hi Florian,
sorry, probably this change should have been part of cf7ffdd.
Should I modify the commit message, or split in two parts?
Paul
> From: Florian Weimer <fweimer@redhat.com>
> Cc: Paul Zimmermann <Paul.Zimmermann@inria.fr>
> Date: Tue, 14 Feb 2023 10:47:11 +0100
>
> * Paul Zimmermann via Libc-alpha:
>
> > ---
> > math/auto-libm-test-out-hypot | 25 +++++++++++++++++++++++++
>
> I wouldn't expect this change in a “regenerate ulps” commit?
>
> Thanks,
> Florian
>
>
next prev parent reply other threads:[~2023-02-14 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 8:50 Paul Zimmermann
2023-02-14 9:47 ` Florian Weimer
2023-02-14 9:55 ` Paul Zimmermann [this message]
2023-02-14 9:58 ` Florian Weimer
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=mwfsb81si2.fsf@coriandre.loria.fr \
--to=paul.zimmermann@inria.fr \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).