Jeeva Sarma writes: > > I have a question regarding tags made on branches. > I have branched our tree with the branch name 2.0.
2.0 is not a branch name. > After some days,I wanted to make a tag on the branch > for QA testing purpose.I checked out from the branch > and then tagged it from that working directory with > cvs tag -r 'tag_on_branch_name' modulename > Is this the correct procedure? Almost certainly not. If that's really the command you typed, you applied a tag of "modulename" to the revision/branch specified by 'tag_on_branch_name'. Usually, you do not specify a specific revision to tag with -r, you just tag the currently checked-out revision in your working directory. And one usually doesn't use the module name as a tag name, it's too confusing. > One developer insists that when he checked out from > the branch,he doesn't get the latest files from that > branch and has to do a > cvs update -r tag_on_branch_name > to get the latest files.As a result,he cannot commit > because of the sticky tag. > I told him that he should get the latest files from > the branch by checking out from the branch regardless > of the tag.Isn't this correct? Who knows? Your description is too confused to follow. Perhaps you could do a "cvs status -v" on one of the files and share it with us so we could get some clue as to what you really did and are doing. -Larry Jones Even my FRIENDS don't do what I want. -- Calvin _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs