NAME
ident - identify RCS keyword strings in files
SYNOPSIS
iiddeenntt [ -qq ] [ -VV ] [ file ... ]
DESCRIPTION
iiddeenntt searches for all instances of the pattern $$keyword:: text $$ in the
named files or, if no files are named, the standard input. These patterns are normally inserted automatically by the RCS commandccoo(1), but can also be inserted manually. The option -qq suppresses the
warning given if there are no patterns in a file. The option -VV prints
iiddeenntt's version number.iiddeenntt works on text files as well as object files and dumps. For exam-
ple, if the C program in ff..cc contains##iinncclluuddee <
ssttaattiicc cchhaarr ccoonnsstt rrccssiidd[[]] ==> ""$$IIdd:: ff..cc,,vv 11..11 11999999//0044//2233 0011::4433::3377 wwssaanncchheezz EExxpp $$"";;
iinntt mmaaiinn(()) {{ rreettuurrnn pprriinnttff((""%%ss\\nn"",, rrccssiidd)) ==== EEOOFF;; }}
and ff..cc is compiled into ff..oo, then the command iiddeenntt ff..cc ff..oo will output ff..cc::$$IIdd:: ff..cc,,vv 11..11 11999999//0044//2233 0011::4433::3377 wwssaanncchheezz EExxpp $$
ff..oo::$$IIdd:: ff..cc,,vv 11..11 11999999//0044//2233 0011::4433::3377 wwssaanncchheezz EExxpp $$
If a C program defines a string like rrccssiidd above but does not use it, lliinntt(1) may complain, and some C compilers will optimize away the string. The most reliable solution is to have the program use the rrccssiidd string, as shown in the example above.iiddeenntt finds all instances of the $$keyword:: text $$ pattern, even if key-
word is not actually an RCS-supported keyword. This gives you informa-
tion about nonstandard keywords like $$XXCCoonnssoorrttiiuumm$$.
KKEEYYWWOORRDDSS Here is the list of keywords currently maintained by ccoo(1). All times are given in Coordinated Universal Time (UTC, sometimes called GMT) bydefault, but if the files were checked out with ccoo's -zzzone option,
times are given with a numeric time zone indication appended.$$AAuutthhoorr$$
The login name of the user who checked in the revision.$$DDaattee$$ The date and time the revision was checked in.
$$HHeeaaddeerr$$
A standard header containing the full pathname of the RCS file, the revision number, the date and time, the author, the state, and the locker (if locked).$$IIdd$$ Same as $$HHeeaaddeerr$$, except that the RCS filename is without a
path.$$LLoocckkeerr$$
The login name of the user who locked the revision (empty if not locked).$$LLoogg$$ The log message supplied during checkin. For iiddeenntt's purposes,
this is equivalent to $$RRCCSSffiillee$$.
$$NNaammee$$ The symbolic name used to check out the revision, if any.
$$RRCCSSffiillee$$
The name of the RCS file without a path.$$RReevviissiioonn$$
The revision number assigned to the revision.$$SSoouurrccee$$
The full pathname of the RCS file.$$SSttaattee$$
The state assigned to the revision with the -ss option of rrccss(1)
or ccii(1). ccoo(1) represents the following characters in keyword values by escapesequences to keep keyword strings well-formed.
char escape sequence tab \\tt newline \\nn space \\004400$$ \\004444
\\ \\\\ IIDDEENNTTIIFFIICCAATTIIOONN Author: Walter F. Tichy. Manual Page Revision: 1.1; Release Date: 1999/04/23. Copyright (C) 1982, 1988, 1989 Walter F. Tichy. Copyright (C) 1990, 1992, 1993 Paul Eggert.SEE ALSO
ci(1), co(1), rcs(1), rcsdiff(1), rcsintro(1), rcsmerge(1), rlog(1), rcsfile(5)Walter F. Tichy, RCS-A System for Version Control, Software-Practice
& Experience 1155, 7 (July 1985), 637-654.
GNU 1999/04/23 IDENT(1)