version 1, including all changes.
.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
IDENT |
|
|
2 |
!!!IDENT |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
KEYWORDS |
|
|
7 |
IDENTIFICATION |
|
|
8 |
SEE ALSO |
|
|
9 |
---- |
|
|
10 |
!!NAME |
|
|
11 |
|
|
|
12 |
|
|
|
13 |
ident - identify RCS keyword strings in files |
|
|
14 |
!!SYNOPSIS |
|
|
15 |
|
|
|
16 |
|
|
|
17 |
__ident__ [[ __-q__ ] [[ __-V__ ] [[ ''file'' ... |
|
|
18 |
] |
|
|
19 |
!!DESCRIPTION |
|
|
20 |
|
|
|
21 |
|
|
|
22 |
__ident__ searches for all instances of the pattern |
|
|
23 |
__$__''keyword''__:__ ''text'' __$__ in the |
|
|
24 |
named files or, if no files are named, the standard |
|
|
25 |
input. |
|
|
26 |
|
|
|
27 |
|
|
|
28 |
These patterns are normally inserted automatically by the |
|
|
29 |
RCS command co(1), but can also be |
|
|
30 |
inserted manually. The option __-q__ suppresses the |
|
|
31 |
warning given if there are no patterns in a file. The option |
|
|
32 |
__-V__ prints __ident__'s version number. |
|
|
33 |
|
|
|
34 |
|
|
|
35 |
__ident__ works on text files as well as object files and |
|
|
36 |
dumps. For example, if the C program in __f.c__ |
|
|
37 |
contains |
|
|
38 |
|
|
|
39 |
|
|
|
40 |
__#include __ |
|
|
41 |
static char const rcsid[[] = |
|
|
42 |
int main() { return printf( |
|
|
43 |
|
|
|
44 |
|
|
|
45 |
and __f.c__ is compiled into __f.o__, then the |
|
|
46 |
command |
|
|
47 |
|
|
|
48 |
|
|
|
49 |
__ident f.c f.o__ |
|
|
50 |
|
|
|
51 |
|
|
|
52 |
will output |
|
|
53 |
|
|
|
54 |
|
|
|
55 |
__ f.c: |
|
|
56 |
$Id: f.c,v 5.4 1993/11/09 17:40:15 eggert Exp $ |
|
|
57 |
f.o: |
|
|
58 |
$Id: f.c,v 5.4 1993/11/09 17:40:15 eggert Exp $ |
|
|
59 |
__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. |
|
|
60 |
|
|
|
61 |
|
|
|
62 |
__ident__ finds all instances of the |
|
|
63 |
__$__''keyword''__:__ ''text'' __$__ pattern, |
|
|
64 |
even if ''keyword'' is not actually an RCS |
|
|
65 |
-supported keyword. This gives you information about |
|
|
66 |
nonstandard keywords like __$XConsortium$__. |
|
|
67 |
!!KEYWORDS |
|
|
68 |
|
|
|
69 |
|
|
|
70 |
Here is the list of keywords currently maintained by |
|
|
71 |
co(1). All times are given in Coordinated Universal |
|
|
72 |
Time ( UTC , sometimes called |
|
|
73 |
GMT ) by default, but if the files were |
|
|
74 |
checked out with __co__'s __-z__''zone'' option, |
|
|
75 |
times are given with a numeric time zone indication |
|
|
76 |
appended. |
|
|
77 |
|
|
|
78 |
|
|
|
79 |
__$Author$__ |
|
|
80 |
|
|
|
81 |
|
|
|
82 |
The login name of the user who checked in the |
|
|
83 |
revision. |
|
|
84 |
|
|
|
85 |
|
|
|
86 |
__$Date$__ |
|
|
87 |
|
|
|
88 |
|
|
|
89 |
The date and time the revision was checked in. |
|
|
90 |
|
|
|
91 |
|
|
|
92 |
__$Header$__ |
|
|
93 |
|
|
|
94 |
|
|
|
95 |
A standard header containing the full pathname of the |
|
|
96 |
RCS file, the revision number, the date and |
|
|
97 |
time, the author, the state, and the locker (if |
|
|
98 |
locked). |
|
|
99 |
|
|
|
100 |
|
|
|
101 |
__$Id$__ |
|
|
102 |
|
|
|
103 |
|
|
|
104 |
Same as __$Header$__, except that the RCS |
|
|
105 |
filename is without a path. |
|
|
106 |
|
|
|
107 |
|
|
|
108 |
__$Locker$__ |
|
|
109 |
|
|
|
110 |
|
|
|
111 |
The login name of the user who locked the revision (empty if |
|
|
112 |
not locked). |
|
|
113 |
|
|
|
114 |
|
|
|
115 |
__$Log$__ |
|
|
116 |
|
|
|
117 |
|
|
|
118 |
The log message supplied during checkin. For __ident__'s |
|
|
119 |
purposes, this is equivalent to |
|
|
120 |
__$RCSfile$__. |
|
|
121 |
|
|
|
122 |
|
|
|
123 |
__$Name$__ |
|
|
124 |
|
|
|
125 |
|
|
|
126 |
The symbolic name used to check out the revision, if |
|
|
127 |
any. |
|
|
128 |
|
|
|
129 |
|
|
|
130 |
__$RCSfile$__ |
|
|
131 |
|
|
|
132 |
|
|
|
133 |
The name of the RCS file without a |
|
|
134 |
path. |
|
|
135 |
|
|
|
136 |
|
|
|
137 |
__$Revision$__ |
|
|
138 |
|
|
|
139 |
|
|
|
140 |
The revision number assigned to the revision. |
|
|
141 |
|
|
|
142 |
|
|
|
143 |
__$Source$__ |
|
|
144 |
|
|
|
145 |
|
|
|
146 |
The full pathname of the RCS |
|
|
147 |
file. |
|
|
148 |
|
|
|
149 |
|
|
|
150 |
__$State$__ |
|
|
151 |
|
|
|
152 |
|
|
|
153 |
The state assigned to the revision with the __-s__ option |
|
|
154 |
of rcs(1) or ci(1). |
|
|
155 |
|
|
|
156 |
|
|
|
157 |
co(1) represents the following characters in keyword |
|
|
158 |
values by escape sequences to keep keyword strings |
|
|
159 |
well-formed. |
|
|
160 |
|
|
|
161 |
|
|
|
162 |
''char escape sequence |
|
|
163 |
''tab __ t |
|
|
164 |
__newline __ n |
|
|
165 |
__space __ 040 |
|
|
166 |
$ 044 |
|
|
167 |
\ \ |
|
|
168 |
__ |
|
|
169 |
!!IDENTIFICATION |
|
|
170 |
|
|
|
171 |
|
|
|
172 |
Author: Walter F. Tichy. |
|
|
173 |
Manual Page Revision: 5.4; Release Date: 1993/11/09. |
|
|
174 |
Copyright 1982, 1988, 1989 Walter F. Tichy. |
|
|
175 |
Copyright 1990, 1992, 1993 Paul Eggert. |
|
|
176 |
!!SEE ALSO |
|
|
177 |
|
|
|
178 |
|
|
|
179 |
ci(1), co(1), rcs(1), rcsdiff(1), rcsintro(1), rcsmerge(1), |
|
|
180 |
rlog(1), rcsfile(5) |
|
|
181 |
Walter F. Tichy, RCS --A System for Version |
|
|
182 |
Control, ''Software--Practice '' |
|
|
183 |
__15__, 7 (July 1985), 637-654. |
|
|
184 |
---- |