f.c:


    $Id: f.c,v (iD $


f.o:


    $Id: f.c,v (iD $


 

  


 If a C program defines a string like


  rcsid above but does not use it,


  lint(1) 

 may complain, and some C compilers will optimize away the string.


The most reliable solution is to have the program use the


  rcsid string, as shown in the example above.


 

  


   ident finds all instances of the


  $ keyword : \ text\  $ pattern, even if


  keyword

 is not actually an r-supported keyword.


This gives you information about nonstandard keywords like


  $XConsortium$ .

 

$Author$

The login name of the user who checked in the revision.

$Date$

The date and time the revision was checked in.

$Header$

A standard header containing the full pathname of the r file, the
revision number, the date and time, the author, the state,
and the locker (if locked).

$Id$

Same as
$Header$ ,
except that the r filename is without a path.

$Locker$

The login name of the user who locked the revision (empty if not locked).

$Log$

The log message supplied during checkin.
For
ident 's
purposes, this is equivalent to
$RCSfile$ .

$Name$

The symbolic name used to check out the revision, if any.

$RCSfile$

The name of the r file without a path.

$Revision$

The revision number assigned to the revision.

$Source$

The full pathname of the r file.

$State$

The state assigned to the revision with the
-s option of
rcs(1)
or
ci(1) .



co(1)
represents the following characters in keyword values by escape sequences
to keep keyword strings well-formed.

<2>char escape sequence


 tab <3>\t


newline <3>\n


space <3>\040


$ \044


\ \\