I've been looking at my CVS book and checked on the web with no luck. What "text" is needed in a module, so cvs commit will write change history into the module(s)?

Thanks.
cmn

CVS uses tags, which are placeholders for specific types of information. When CVS encounters a tag that it understands in a text file, it replaces the tag with a string containing the specified information. Afterwards, it continues to recognize tags that have already been expanded, and replaces them on each commit. An example of a common tag is the '$Date$' tag. CVS will replace this with a time/date stamp string when the module is committed to the repository. For putting a history into the file, the $Log$ tag can be used. Its behavior is a bit different, in that it doesn't throw away the previous instance, but appends new information on each commit, thus leaving a history trail. Usually CVS tags would be placed in comment-blocks in the code, but CVS doesn't care where it finds tags; it will replace them anywhere it finds them. Your CVS book should list all of the possible tags and their purpose and behavior.
--- rod.

1 members found this post helpful.

Thanks again. When I read tags, I was thinking of tagging at the command line. Maybe they're the same thing as tags like $Log$, but the word tags took me in the wrong direction.