Branch 0.3.5 created

[Luigi Ballabio-2]

Hi all,
        I just created a CVS branch for release 0.3.5 with tag  
"R000305f0-branch".  Bug-fixes to be applied before release must be  
committed on this branch. As usual, new code and features must go on  
the trunk and will appear in the release after 0.3.5.

Later,
        Luigi

[Dirk Eddelbuettel]

On Thu, Mar 11, 2004 at 03:12:01PM +0100, Luigi Ballabio wrote:
>
> Hi all,
> I just created a CVS branch for release 0.3.5 with tag  
> "R000305f0-branch".  Bug-fixes to be applied before release must be  
> committed on this branch. As usual, new code and features must go on  
> the trunk and will appear in the release after 0.3.5.

Ok, so far CVS neophytes like myself, what is the checkout command for a
branch? RTFmanpage suggests 'cvs -r R000305f0-branch checkout' (given a
suitable CVSROOT definitiont, cvs login, etc pp)  ?   Would that do?

Being a self-professed empiricist I guess I should just try :)

Dirk

--
The relationship between the computed price and reality is as yet unknown.  
                                             -- From the pac(8) manual page

[Luigi Ballabio-2]

On 2004.03.11 16:29, Dirk Eddelbuettel wrote:

> On Thu, Mar 11, 2004 at 03:12:01PM +0100, Luigi Ballabio wrote:
> > I just created a CVS branch for release 0.3.5 with tag
> > "R000305f0-branch".  Bug-fixes to be applied before release must be
> > committed on this branch. As usual, new code and features must go
> > on the trunk and will appear in the release after 0.3.5.
>
> Ok, so far CVS neophytes like myself, what is the checkout command  
> for a branch? RTFmanpage suggests 'cvs -r R000305f0-branch  
> checkout' (given a suitable CVSROOT definitiont, cvs login, etc  
> pp)  ?   Would that do?

Yes, I guess it would do. Once you'll have the module checked out,  
you'll need to run ./boostrap before starting the usual configure  
mantra.

Oh, and the sources will probably change before release, so don't use  
precious final version numbers for your Debian stuff yet :)

Later,
        Luigi

[Ferdinando M. Ametrano-3]

Hi Dirk

>Ok, so far CVS neophytes like myself, what is the checkout command for a
>branch? RTFmanpage suggests 'cvs -r R000305f0-branch checkout' (given a
>suitable CVSROOT definitiont, cvs login, etc pp)  ?   Would that do?

I suggest you to read http://quantlib.org/cvs.html

In short (anonymous checkout):
export CVSROOT=:pserver:[hidden email]:/cvsroot/quantlib
cvs login
cvs -z3 co -P -r R000305f0-branch QuantLib

In short (developer checkout):
export CVSROOT=[hidden email]:/cvsroot/quantlib
export CVS_RSH=ssh
cvs -z3 co -P -r R000305f0-branch QuantLib

and you're done

ciao -- Nando

[enrico.sirola-2]

>>>>> "Dirk" == Dirk Eddelbuettel <[hidden email]> writes:

    Dirk> On Thu, Mar 11, 2004 at 03:12:01PM +0100, Luigi Ballabio
    Dirk> wrote:
    >>  Hi all, I just created a CVS branch for release 0.3.5 with tag
    >> "R000305f0-branch".  Bug-fixes to be applied before release
    >> must be committed on this branch. As usual, new code and
    >> features must go on the trunk and will appear in the release
    >> after 0.3.5.

    Dirk> Ok, so far CVS neophytes like myself, what is the checkout
    Dirk> command for a branch? RTFmanpage suggests 'cvs -r
    Dirk> R000305f0-branch checkout' (given a suitable CVSROOT
    Dirk> definitiont, cvs login, etc pp) ?  Would that do?

I'd suggest cvs co -r <tagname>
cvs -r <stuff> makes checked-out files read only
bye,
e.

--
Enrico Sirola <[hidden email]>