[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnubg] 0.13.x branched in CVS
From: |
Jim Segrave |
Subject: |
Re: [Bug-gnubg] 0.13.x branched in CVS |
Date: |
Thu, 16 Jan 2003 15:42:38 +0100 |
User-agent: |
Mutt/1.4i |
On Thu 16 Jan 2003 (15:30 +0100), Achim Mueller wrote:
> Am Mit, 2003-01-15 um 17.09 schrieb Gary Wong:
>
> > I've added a CVS branch with tag "branch-0-13". Please commit bug fixes
> > to both this branch and the trunk (if appropriate), but new features to
> > the trunk only.
>
> Sorry for the questions, but I'm too tired at the moment to read the big
> cvs documentation. I use a small script for getting the current sources:
>
> export CVS_RSH=ssh
> export address@hidden:/cvsroot/gnubg
> cd $HOME/local/src
> cvs -z3 address@hidden:/cvsroot/gnubg co gnubg
>
>
> 1. How do I change it to get the new stable and the devel tree?
>
> When I commit patches (usually only "po/de.po" or the documentation) I
> use the command:
> "cvs commit [Path/to/file]"
What I think should work (haven't tried it yet:
to get the current devel tree:
cvs co gnubg
To get the 0.13 tree (I'd suggest simply getting it in another
subdirectory):
cvs co -rbranch-0-13 gnubg
> 2. What have I to do now to put it into both trees?
Check them in from the different directories (the CVS subdirectories
have files which record the tags for where things come from).
This is how we do it with CVS at work and I'd expect it to be the
same.
--
Jim Segrave address@hidden