|
From: | Kai Torben Ohlhus |
Subject: | [Octave-bug-tracker] [bug #57309] ode23s removed from odepkg on BitBucket not in core Octave |
Date: | Wed, 4 Dec 2019 21:44:03 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36 |
Update of bug #57309 (project octave): Severity: 3 - Normal => 1 - Wish Priority: 5 - Normal => 3 - Low Status: Need Info => Postponed _______________________________________________________ Follow-up Comment #4: Thank you for investigating the state of "ode23s". Thus an interested developer can pick up on moving "ode23s" into Octave core. In the meantime, I overhauled the wiki page for the "odepkg" https://wiki.octave.org/Odepkg but with the current description "ode23s" would not be usable because of https://bitbucket.org/odepkg/odepkg/commits/17b0e2c5e5f4a11e86e9af20166da6d1beb01ce5?at=octave43 Is it possible to rearrange the Bitbucket repo, such that https://bitbucket.org/odepkg/odepkg/commits/17b0e2c5e5f4a11e86e9af20166da6d1beb01ce5?at=octave43 is reverted and "octave43" is merged to "default" and "stable" gets closed? I think that your repo does not have to offer support for Octave 4.2 any longer. If you like, I can help out (https://bitbucket.org/account/user/siko1056/). _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?57309> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |