Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
Bo Berglund wrote: > What it would do is to reset all files in the sandbox to the first > revision existing in the current branch (so if the command was invoked > on a non-branched sandbox it would go back to all files at rev 1.1. > cvs update -r<branch tag> -s > Where the -s option directs cvs to grab the branch start and make it > sticky, it is somewhat like cvs update -A to remove stickiness, except > it "sticks" the revision on each file at the branch point. > The -s option would not be valid unless -r specifies a valid branch > tag. What may be missing here is the reference to the originator branch (could be the trunk), from where the branch got created. Requiring that the file exists both in the current branch and the originator branch (that is, really getting only the files that have been "branched") would automatically exclude the trunk -- there's no originator branch ever on the trunk. When you want to update to the branch start, most often you don't want to update to the first revision on the branch, but to the revision on the originator branch that was used to create the branch. (Like when you want to create another branch from the same point.) Gerhard