The standard meanings of the common client options -l and -R apply. The other option that can be used with the status command, -v, may be used to include tag information. tag tag [ -b ] [ -c ] [ -d ] [ -D date | -r rev ] [ -f ] [ -F ] [ -l | R ] tag [ file ... ] Assign a tag to the sandbox revisions of a set of files. You can use the status -v command to list the existing tags for a file. The tag must start with a letter and must consist entirely of letters, numbers, dashes ( - ) and underscores ( _ ). Therefore, while you might want to tag your hello project with 1.0 when you release Version 1.0, you'll need to tag it with something like hello-1_0 instead. The standard meanings of the common client options -D, -f, -l, -r, and -R apply. Additional options are listed in Table 14.36. Table 14-36. tag Options Option -b -c -d -F Description Make a branch. Check for changes. Make sure the files are not locally modified before tagging. Delete the tag. Force. Move the tag from its current revision to the one specified. CVS and RCS Since the -d option throws away information that might be important, it is recom- mended that you use it only when absolutely necessary. It is usually better to create a different tag with a similar name. unedit unedit [ -l | -R ] [ file ... ] Abandon file modifications and make the file read-only again. Watchers will be notified. The standard meanings of the common client options -l and -R apply. CVS User Reference | 703