public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Patrick Alken <patrick.alken@Colorado.EDU>
Cc: "gsl-discuss@sourceware.org" <gsl-discuss@sourceware.org>
Subject: Re: new GSL version
Date: Fri, 24 May 2013 19:36:00 -0000	[thread overview]
Message-ID: <519FC153.7030503@colorado.edu> (raw)
In-Reply-To: <CAKDqugRByMUqy0s0r2trq=z3u3N4XkaCW=zANQ=MRDENB6dHig@mail.gmail.com>

I have a laptop running Mac OS X 10.6, and just ran make check on the 
latest repository with no errors. Does anyone have failures they can 
send to me?

On 05/24/2013 10:38 AM, Rhys Ulerich wrote:
>
> >   I think its time to make a new release of GSL (v1.16). There have 
> been a number of bugfixes and new features added in the last couple 
> years. I don't mind taking the lead on this...
>
> Thank you.
>
> I know of nothing critical but believe we want to have make check come 
> back clean at default optimization on OS X. It has not, I think due to 
> SVD tolerances, for some time. Do we have some sort of GNU-provided 
> continuous integration server available on which these types of 
> portability issues might be flushed out on an ongoing basis?
>
> I very much like your idea of just collecting up the bug reports and 
> moving on. Some sort of a post release bug fix effort would do well to 
> harness people's interest in contributing so that we might add some 
> pep to the community.
>
> - Rhys
>

  parent reply	other threads:[~2013-05-24 19:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 16:00 Patrick Alken
2013-05-24 18:51 ` Brian Gladman
2013-05-24 20:50   ` Patrick Alken
2013-05-24 21:12     ` Brian Gladman
     [not found] ` <CAKDqugRByMUqy0s0r2trq=z3u3N4XkaCW=zANQ=MRDENB6dHig@mail.gmail.com>
2013-05-24 19:36   ` Patrick Alken [this message]
2013-05-26  7:28 ` Tuomo Keskitalo

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=519FC153.7030503@colorado.edu \
    --to=patrick.alken@colorado.edu \
    --cc=gsl-discuss@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).