[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Implications of indexing changes for code that calls Fortran
From: |
Olaf Till |
Subject: |
Re: Implications of indexing changes for code that calls Fortran |
Date: |
Tue, 3 Jan 2017 10:55:15 +0100 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On Mon, Jan 02, 2017 at 07:44:05PM -0500, John W. Eaton wrote:
> I'm attaching my changes. Could someone help me get these applied in the
> upstream Octave Forge packages? The affected packages are:
>
> control
> linear-algebra
> nlwing2
> odepkg
> optim
> optiminterp
> tisean
Thank you for caring also for the packages. Since I think Carnë
currently can't do it, and since you would have done it yourself if
you had a login, I've been bold enough to apply and push your
changesets to:
linear-algebra
nlwing2
odepkg
optim
tisean
The changeset for control did not apply, however. I'll still look into
optiminterp, once I've re-loaded the SVN stuff.
Olaf
--
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net
signature.asc
Description: Digital signature
- Implications of indexing changes for code that calls Fortran, John W. Eaton, 2017/01/02
- Re: Implications of indexing changes for code that calls Fortran, Nicholas Jankowski, 2017/01/02
- Re: Implications of indexing changes for code that calls Fortran, John W. Eaton, 2017/01/02
- Re: Implications of indexing changes for code that calls Fortran, John W. Eaton, 2017/01/03
- Re: Implications of indexing changes for code that calls Fortran, Olaf Till, 2017/01/03
- Re: Implications of indexing changes for code that calls Fortran, Olaf Till, 2017/01/03
- Re: Implications of indexing changes for code that calls Fortran, John W. Eaton, 2017/01/03
- Re: Implications of indexing changes for code that calls Fortran, PhilipNienhuis, 2017/01/07
- Re: Implications of indexing changes for code that calls Fortran, PhilipNienhuis, 2017/01/03