info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: partial branch problem


From: Jim.Hyslop
Subject: RE: partial branch problem
Date: Fri, 30 Jan 2004 09:45:14 -0500

Jon Ringle [mailto:address@hidden wrote:
> After doing my first branch based on a tag created by a build 
> script, I 
> discovered that the build script creates the tag on a 
> subdirectory of the 
> module rather than on the module itself using something like:
> 
> cvs tag -R sometag module/sub1
[...]
> However, there are other subdirectories of the module that 
> need to be a part 
> of the branch. Fortunately, the other subdirectories are 
> tracking 3rd party 
> sources that change very infrequently.
> 
> I was thinking that I might be able to correct the situation by doing:
> 
> cvs tag -R sometag module/sub2
> cvs rtag -b -r sometag branch_sometag module/sub2
[...]
> Is there another approach that would be better? (I do plan on 
> fixing the build 
> script that created this problem in the first place)
If the whole module needs the tag, then just issue the tag command at the
root directory for the module:

cvs rtag -R sometag branch_sometag module

When CVS processes sub1, it will complain about the existing tags, saying
something like "tag branch_sometag exists, not moving it". You can ignore
these complaints. CVS won't move the tags, unless you use the -F flag
(which, from the sounds of it, you don't want to do).

-- 
Jim Hyslop 
Senior Software Designer 
Leitch Technology International Inc. (<http://www.leitch.com/>) 
Columnist, C/C++ Users Journal (<http://www.cuj.com/experts>) 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]