[cvsnt] tagging and branching
Bo Berglund
Bo.Berglund at system3r.se
Thu Oct 30 23:56:07 GMT 2003
The export command should be:
cvs export -r myTag_For_myBranch -d myLocalDirectory myModule
It will get the files in myModule and below and put these in your local directory
myLocalDirectory. The files will be those that existed at the point in time when you
set the tag myTag_For_myBranch (obviously this means that the files are from the
branch since you tagged on the branch).
Files that had not been changed since you started work on the branch are still part
of the branch even though they do not carry the extra revision numbers and they are
also tagged. THe idea here is that by tagging on the branch and then exporting that
you recreate the working file set completely and you can compile an executable just
like the one you did at that time. So you need all of these files.
/Bo
-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Ian Huynh
Sent: den 30 oktober 2003 22:40
To: cvsnt at cvsnt.org
Subject: RE: [cvsnt] tagging and branching
when excuting the cmd below for my branch
cvs rtag -r myBranch myTag_For_myBranch myModule
the cmd executed succesfully, but when showing status of any files in the maintrunk,
the myTag_For_myBranch shows up for all of those files.
How does that work?
cvs export -r myTag_For_myBranch myLocalDirectory
which version does cvs get my files from? main trunk or myBranch ?
> -----Original Message-----
> From: cvsnt-bounces at cvsnt.org
> [mailto:cvsnt-bounces at cvsnt.org]On Behalf
> Of Oliver Giesen
> Sent: Tuesday, October 28, 2003 1:01 AM
> To: cvsnt at cvsnt.org
> Subject: Re: [cvsnt] tagging and branching
>
>
> Ian Huynh wrote:
>
> > I've looked at the documentation and it eludes to -r option
> >
> > eg.
> > cvs rtag -r myBranch myTag_For_myBranch
>
> ...plus the module name of course, but yes, that's what you
> need to do.
>
>
> > but -r is described in the help file as followed:
> >
> > -r tag
> > Only tag those files that contain tag. This can be used to rename a
> > tag: tag only the files identified by the old tag, then delete the
> > old tag, leaving the new tag on exactly the same files as
> the old tag.
> >
> >
> > My questions are:
> >
> > 1. i don't want the old tag removed
>
> That was only an example of what the -r option /could/ be
> used for. The
> actions described above would look something like this:
>
> cvs rtag -rOldTag NewTag Module
> cvs rtag -d OldTag
>
> ..., i.e. the tag removal is always a separate and conscious action.
>
>
> > 2. what about new files added to myBranch? Would they have a tag
> > myBranch ? If not, how would they be included in
> > myTag_For_myBranch?
>
> That's exactly the point: They wouldn't be on the branch if
> they didn't
> have the branch tag. So, yes, all files added to that branch will
> indeed automatically have that branch tag.
>
> Hope this helps.
>
> --
> Oliver
> ---- ------------------
> JID: ogiesen at jabber.org
> ICQ: 18777742 (http://wwp.icq.com/18777742)
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
>
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
More information about the cvsnt
mailing list