From: Brian Gough <bjg@gnu.org>
To: Rhys Ulerich <rhys.ulerich@gmail.com>
Cc: gsl-discuss@sourceware.org
Subject: Re: libflame version 4.0 announced
Date: Wed, 17 Feb 2010 21:20:00 -0000 [thread overview]
Message-ID: <878warr23x.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <4a00655d1002132215r6aec8a99o45dfdcd65e9b49fb@mail.gmail.com>
At Sun, 14 Feb 2010 00:15:04 -0600,
Rhys Ulerich wrote:
> There was some talk several months back on using libflame underneath
> GSL 2.0. libflame 4.0 was announced today, and it both includes
> row-major support and eliminates their lingering Fortran/LAPACK
> dependencies. The release announcement follows...
Hooray.
next prev parent reply other threads:[~2010-02-17 21:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 6:15 Rhys Ulerich
2010-02-17 21:20 ` Brian Gough [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-02 8:19 GSL extension ode-initval2-1.0 released Tuomo Keskitalo
2010-02-16 23:36 ` libflame version 4.0 announced Gerard Jungman
2010-02-17 21:20 ` Brian Gough
2010-02-17 22:49 ` Gerard Jungman
2010-02-17 23:10 ` Rhys Ulerich
2010-02-19 18:19 ` Brian Gough
2010-02-17 22:51 ` James Amundson
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=878warr23x.wl%bjg@network-theory.co.uk \
--to=bjg@gnu.org \
--cc=gsl-discuss@sourceware.org \
--cc=rhys.ulerich@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 read-only IMAP folder(s) and NNTP newsgroup(s).