From: "Jean-François Caron" <jfcaron@phas.ubc.ca>
To: Patrick Alken <patrick.alken@Colorado.EDU>
Cc: gsl-discuss@sourceware.org
Subject: Re: Next Version?
Date: Thu, 19 Jun 2014 20:13:00 -0000 [thread overview]
Message-ID: <C9FD9F00-B0A7-44E5-9D94-7E286CE5A8CD@phas.ubc.ca> (raw)
In-Reply-To: <53A3435C.5070105@colorado.edu>
On Jun 19, 2014, at 13:09 , Patrick Alken <patrick.alken@Colorado.EDU> wrote:
> On 06/19/2014 07:58 PM, Jean-François Caron wrote:
>> Hello, I am wondering if anyone has an update on when we might see the next version of GSL? Is it something like “in the next month”, “by the end of summer”, or “next year”?
>>
>> I don’t need any details, I’m just being impatient because my contribution is supposed to appear in the next version, and I wish to make a patch for CERN’s ROOT that will use the new feature. So just a short answer will be enough to satisfy me. = )
>>
>> Jean-François
>>
>
> By the way, why can't you just use the git version in your work? Do you
> really need an official release?
>
> Patrick
Oh there is no problem for me using the git version, along with a ROOT checkout that I also modified to use the Steffen interpolation. I have a feeling that most users however will not be compiling their own versions of GSL or even ROOT, so putting everything into the official versions has been on my mind. It’s just an extra thing on my mental todo list that I’ve been wondering about.
Jean-François
next prev parent reply other threads:[~2014-06-19 20:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 17:59 Jean-François Caron
2014-06-19 18:01 ` Rhys Ulerich
2014-06-19 20:08 ` Patrick Alken
2014-06-20 0:06 ` Gerard Jungman
2014-06-19 20:09 ` Patrick Alken
2014-06-19 20:13 ` Jean-François Caron [this message]
2014-06-26 20:11 ` Patrick Alken
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=C9FD9F00-B0A7-44E5-9D94-7E286CE5A8CD@phas.ubc.ca \
--to=jfcaron@phas.ubc.ca \
--cc=gsl-discuss@sourceware.org \
--cc=patrick.alken@Colorado.EDU \
/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).