I have been given responsibility for managing branchs in a module of our cvs repository.
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 When I went to create the branch, I had assumed that the tag I was basing the branch on was done on the whole module. I did: cvs rtag -b -r sometag branch_sometag module When I do a checkout on the on the branch_sometag branch with: cvs co -r branch_sometag module my working directory only contains files from module/sub1. I understand that this is due to the original creation of sometag. 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 for each subdirectory that was missed by the initial tag. If I take these corrective steps, when I do another: cvs co -r branch_sometag module should I expect to get the whole module in my working directory? Is there another approach that would be better? (I do plan on fixing the build script that created this problem in the first place) Thanks, Jon _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
