From: "Brian Gough" <bjg@network-theory.co.uk>
To: Lowell Johnson <ldj00@sio.midco.net>
Cc: picca@synchrotron-soleil.fr, gsl-discuss@sources.redhat.com
Subject: Re: cvs version: make check FAIL
Date: Thu, 01 Jun 2006 12:33:00 -0000 [thread overview]
Message-ID: <17534.56437.98460.288069@hp2.network-theory.co.uk> (raw)
In-Reply-To: <200605241728.02573.ldj00@sio.midco.net>
Lowell Johnson writes:
> Sure, that sounds fine to me. The cost of the extra fabs() is rather
> trivial, but avoiding it will save a few clock cycles.
>
> I've attached a patch to be used in place of the earlier patch.
Thanks, now added to the sources.redhat.com repository.
--
Brian Gough
Network Theory Ltd,
Publishing Free Software Manuals --- http://www.network-theory.co.uk/
prev parent reply other threads:[~2006-06-01 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 22:03 Giulio Bottazzi
2006-05-24 2:09 ` Lowell Johnson
2006-05-24 6:42 ` Lowell Johnson
2006-05-24 14:28 ` picca
2006-05-25 20:11 ` Lowell Johnson
2006-05-25 20:12 ` Gerard Jungman
2006-05-25 20:18 ` Gerard Jungman
2006-05-29 16:10 ` Giulio Bottazzi
2006-06-01 12:33 ` Brian Gough [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=17534.56437.98460.288069@hp2.network-theory.co.uk \
--to=bjg@network-theory.co.uk \
--cc=gsl-discuss@sources.redhat.com \
--cc=ldj00@sio.midco.net \
--cc=picca@synchrotron-soleil.fr \
/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).