[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Depreciated Functions
From: |
Paul Kienzle |
Subject: |
Re: Depreciated Functions |
Date: |
Fri, 9 Sep 2005 20:18:21 -0400 |
On http://www.psc.edu/~semke/cvs_branches.html it says:
To create a branch from a tagged revision of my_module, use the command
cvs rtag -r Tagname -b Branchname my_module
So using the latest release tag R2005-06-13 we can at any point create
a 2.1.xx maintenance branch for octave-forge.
- Paul
On Sep 9, 2005, at 11:49 AM, Quentin Spencer wrote:
Paul Kienzle wrote:
I would like octave-forge to be cruft free for the 3.0 release, so it
should depend on functions and syntax in 2.9.x.
There is a lot of cruft in the C++ functions for supporting older
versions of octave. Basically anything in #if is suspicious.
There was a discussion a while back on the Octave-forge list about
branching Octave forge so that the main CVS could follow 2.9.x and
prepare for 3.0. I have only a minimum knowledge of using CVS--has
this been done, or how does one go about doing it? If some of us were
to begin making 2.9.x changes could someone go back and branch from an
older release? As far as I'm concerned, octave-forge is functional
enough on 2.1.71--I suggest we move ahead and only make bug fixes for
2.1.x if something critical comes up.
-Quentin
Re: Depreciated Functions, Bill Denney, 2005/09/09