Shouldn't we use some of these keywords in the source code?
My thoughts are that after tagging the source for a release and then
doing the export then it is obvious to anyone even outside the usual
classpath developer what version of the file they are dealing with and
when it was last edited, etc.
Brian
RCS Keywords
============
This is a list of the keywords that RCS currently (in release
5.6.0.1) supports:
`$Author$'
The login name of the user who checked in the revision.
`$Date$'
The date and time (UTC) the revision was checked in.
`$Header$'
A standard header containing the full pathname of the RCS file,
the revision number, the date (UTC), the author, the state, and
the locker (if locked). Files will normally never be locked when
you use CVS.
`$Id$'
Same as `$Header$', except that the RCS filename is without a path.
`$Name$'
Tag name used to check out this file.
`$Locker$'
The login name of the user who locked the revision (empty if not
locked, and thus almost always useless when you are using CVS).
`$Log$'
The log message supplied during commit, preceded by a header
containing the RCS filename, the revision number, the author, and
the date (UTC). Existing log messages are *not* replaced.
Instead, the new log message is inserted after `$Log:...$'. Each
new line is prefixed with a "comment leader" which RCS guesses
from the file name extension. It can be changed with `cvs admin
-c'. *Note admin options::. This keyword is useful for
accumulating a complete change log in a source file, but for
several reasons it can be problematic. *Note Log keyword::.
`$RCSfile$'
The name of the RCS file without a path.
`$Revision$'
The revision number assigned to the revision.
`$Source$'
The full pathname of the RCS file.
`$State$'
The state assigned to the revision. States can be assigned with
`cvs admin -s'--*Note admin options::.
--
|-------------------------------|Software Engineer
|Brian Jones |[EMAIL PROTECTED]
|[EMAIL PROTECTED] |http://www.nortel.net
|http://www.classpath.org/ |-------------------------------
