From: Rhys Ulerich <rhys.ulerich@gmail.com>
To: Patrick Alken <patrick.alken@colorado.edu>
Cc: gsl-discuss@sourceware.org
Subject: Re: [PATCH] Add Greville abscissae functionality to B-splines
Date: Mon, 15 Jun 2009 18:14:00 -0000 [thread overview]
Message-ID: <4a00655d0906151113y5efb05a7gde0b73d7afc9d0bf@mail.gmail.com> (raw)
In-Reply-To: <20090615173917.GA31020@hippogriff.homeunix.org>
Hi Patrick,
I noticed in the commit there were changes made to install.sh
(http://git.savannah.gnu.org/gitweb/?p=gsl.git;a=commit;h=ccccc3cb7630ea43bdf365bcbaec71e31f8aea91).
Were those deliberate?
- Rhys
On Mon, Jun 15, 2009 at 12:39 PM, Patrick
Alken<patrick.alken@colorado.edu> wrote:
> Nice work, I have added your patch to the repository and
> inserted the appropriate gsl_bspline_free's in test.c.
>
> Patrick
>
> On Mon, Jun 15, 2009 at 09:43:46AM -0500, Rhys Ulerich wrote:
>> Thanks guys.
>>
>> FYI, I woke up this morning and realized I forgot a gsl_bspline_free
>> call at the bottom of each of the unit test blocks in test.c.
>>
>> - Rhys
>>
>> On Mon, Jun 15, 2009 at 5:26 AM, Brian Gough<bjg@network-theory.co.uk> wrote:
>> > At Sun, 14 Jun 2009 12:02:10 -0500,
>> > Rhys Ulerich wrote:
>> >> This change adds computing Greville abscissae to the GSL B-spline
>> >> routines. Updates to unit tests and documentation are included.
>> >> The routines are written so that if the b-spline classes have lower
>> >> continuity basis added later (i.e. by adding multiple knots per
>> >> interior breakpoint), these should continue to do the right thing.
>> >
>> > Cool. I'll let Patrick take care of these.
>> >
>> > --
>> > Brian Gough
>> >
>> >
>
next prev parent reply other threads:[~2009-06-15 18:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 17:02 Rhys Ulerich
2009-06-15 10:30 ` Brian Gough
2009-06-15 14:44 ` Rhys Ulerich
2009-06-15 17:38 ` Patrick Alken
2009-06-15 18:14 ` Rhys Ulerich [this message]
2009-06-15 18:31 ` Patrick Alken
2009-06-17 21:54 ` Rhys Ulerich
2009-06-17 22:11 ` Patrick Alken
2009-06-17 22:52 ` Rhys Ulerich
2009-07-05 1:10 ` 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=4a00655d0906151113y5efb05a7gde0b73d7afc9d0bf@mail.gmail.com \
--to=rhys.ulerich@gmail.com \
--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).