From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] ppc ulps fixes
Date: Mon, 30 Jan 2006 22:31:00 -0000 [thread overview]
Message-ID: <20060130223051.3F838180C27@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Monday, 30 January 2006 17:41:09 +0100 <20060130164109.GO4625@sunsite.mff.cuni.cz>
> I think it is better to merge ulps results rather than regenerate, that way
> we don't suddenly start getting many errors when using slightly older
> compilers.
I must confess I didn't really know what to do with ulps updates, and I
don't think I had ever done one before. I just did what seemed to be the
most obvious thing from README.libm-test.
Thanks,
Roland
prev parent reply other threads:[~2006-01-30 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 16:41 Jakub Jelinek
2006-01-30 17:16 ` Steve Munroe
2006-01-30 22:31 ` Roland McGrath [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=20060130223051.3F838180C27@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.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).