|
From: | Hg200 |
Subject: | [Octave-bug-tracker] [bug #57471] streamtube.m should use surface object rather than patch object |
Date: | Sun, 23 Feb 2020 05:05:16 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0 |
Follow-up Comment #13, bug #57471 (project octave): Thanks for the twist improvement. "bug57471_ostreamtube_v2.patch" + "bug57471_streamtube_v2.patch" are a bit better and I also recognize the missing reference in stream3 + streamline. I made a fresh build and ran some streamline validation scripts. No findings. I have not tested on the current stable branch. But from my side I agree to do the merge into stable. I don't expect any technical trouble. The only point I can think of is whether everyone is now okay with the doc sections (translation). But to be sure, a complete check by a native speaker is necessary. BTW I was always afraid to ask: Is it correct that the standard procedure is to push patches and new functions on the default branch and after a while (before a release) the stable branch is overwritten by the default branch? Is there a possibility to tag a commit so that it will be merged to stable only in a major release (e.g. 7.0 instead 6.1)? _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?57471> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |