1IDENT(1)                    General Commands Manual                   IDENT(1)
2
3
4

NAME

6       ident - identify RCS keyword strings in files
7

SYNOPSIS

9       ident [ -q ] [ -V ] [ file ... ]
10

DESCRIPTION

12       ident searches for all instances of the pattern $keyword: text $ in the
13       named files or, if no files are named, the standard input.
14
15       These patterns are normally inserted automatically by the  RCS  command
16       co(1), but can also be inserted manually.  The option -q suppresses the
17       warning given if there are no patterns in a file.  The option -V prints
18       RCS's version number.
19
20       ident works on text files as well as object files and dumps.  For exam‐
21       ple, if the C program in f.c contains
22
23              #include <stdio.h>
24              static char const rcsid[] =
25                "$Id: f.c,v 5.4 1993/11/09 17:40:15 eggert Exp $";
26              int main() { return printf("%s\n", rcsid) == EOF; }
27
28       and f.c is compiled into f.o, then the command
29
30              ident  f.c  f.o
31
32       will output
33
34              f.c:
35                  $Id: f.c,v 5.4 1993/11/09 17:40:15 eggert Exp $
36              f.o:
37                  $Id: f.c,v 5.4 1993/11/09 17:40:15 eggert Exp $
38
39       If a C program defines a string like rcsid above but does not  use  it,
40       lint(1)  may  complain,  and  some  C  compilers will optimize away the
41       string.  The most reliable solution is to  have  the  program  use  the
42       rcsid string, as shown in the example above.
43
44       ident finds all instances of the $keyword: text $ pattern, even if key‐
45       word is not actually an RCS-supported keyword.  This gives you informa‐
46       tion about nonstandard keywords like $XConsortium$.
47
48       The pattern normally requires a colon and a space immediately after the
49       keyword and a space immediately before the terminating $, but for  Sub‐
50       version  1.2  (and  later) compatibility, ident will also recognize the
51       pattern $keyword:: text $ (i.e., two colons and a space) and  the  pat‐
52       tern  $keyword:: text #$  (likewise, with a hash before the terminating
53       $).  These are the fixed-width keyword syntax.  To summarize, the three
54       recognized patterns are:
55
56              $keyword: text $
57              $keyword:: text $
58              $keyword:: text #$
59

KEYWORDS

61       Here  is the list of keywords currently maintained by co(1).  All times
62       are given in Coordinated Universal Time (UTC, sometimes called GMT)  by
63       default,  but  if  the  files were checked out with co's -zzone option,
64       times are given with a numeric time zone indication appended.
65
66       $Author$
67              The login name of the user who checked in the revision.
68
69       $Date$ The date and time the revision was checked in.
70
71       $Header$
72              A standard header containing the full RCS file name,  the  revi‐
73              sion  number,  the date and time, the author, the state, and the
74              locker (if locked).
75
76       $Id$   Same as $Header$, except that  the  RCS  file  name  is  without
77              directory components.
78
79       $Locker$
80              The login name of the user who locked the revision (empty if not
81              locked).
82
83       $Log$  The log message supplied during checkin.  For ident's  purposes,
84              this is equivalent to $RCSfile$.
85
86       $Name$ The symbolic name used to check out the revision, if any.
87
88       $RCSfile$
89              The RCS file name without directory components.
90
91       $Revision$
92              The revision number assigned to the revision.
93
94       $Source$
95              The full RCS file name.
96
97       $State$
98              The  state assigned to the revision with the -s option of rcs(1)
99              or ci(1).
100
101       co(1) represents the following characters in keyword values  by  escape
102       sequences to keep keyword strings well-formed.
103
104              char     escape sequence
105              tab      \t
106              newline  \n
107              space    \040
108              $        \044
109              \        \\
110

IDENTIFICATION

112       Author: Walter F. Tichy.
113       Manual Page Revision: 5.9.4; Release Date: 2019-02-02.
114       Copyright © 2010-2015 Thien-Thi Nguyen.
115       Copyright © 1990, 1992, 1993 Paul Eggert.
116       Copyright © 1982, 1988, 1989 Walter F. Tichy.
117

SEE ALSO

119       ci(1), co(1), rcs(1), rcsdiff(1), rcsmerge(1), rlog(1), rcsfile(5).
120
121       Walter  F. Tichy, RCS--A System for Version Control, Software--Practice
122       & Experience 15, 7 (July 1985), 637-654.
123
124       The full documentation for RCS is maintained as a Texinfo  manual.   If
125       the  info(1)  and RCS programs are properly installed at your site, the
126       command
127
128              info rcs
129
130       should give you access to the complete manual.  Additionally,  the  RCS
131       homepage:
132
133              http://www.gnu.org/software/rcs/
134
135       has news and links to the latest release, development site, etc.
136
137
138
139GNU RCS 5.9.4                     2019-02-02                          IDENT(1)
Impressum