Penguin
Recent Changes
Annotated edit history of rcs(1) version 1, including all changes. View license author blame.
Rev Author # Line
1 perry 1 RCS
2 !!!RCS
3 NAME
4 SYNOPSIS
5 DESCRIPTION
6 OPTIONS
7 COMPATIBILITY
8 FILES
9 ENVIRONMENT
10 DIAGNOSTICS
11 IDENTIFICATION
12 SEE ALSO
13 BUGS
14 ----
15 !!NAME
16
17
18 rcs - change RCS file attributes
19 !!SYNOPSIS
20
21
22 __rcs__ ''options file'' ...
23 !!DESCRIPTION
24
25
26 __rcs__ creates new RCS files or changes
27 attributes of existing ones. An RCS file
28 contains multiple revisions of text, an access list, a
29 change log, descriptive text, and some control attributes.
30 For __rcs__ to work, the caller's login name must be on
31 the access list, except if the access list is empty, the
32 caller is the owner of the file or the superuser, or the
33 __-i__ option is present.
34
35
36 Pathnames matching an RCS suffix denote
37 RCS files; all others denote working files.
38 Names are paired as explained in ci(1). Revision
39 numbers use the syntax described in
40 ci(1).
41 !!OPTIONS
42
43
44 __-i__
45
46
47 Create and initialize a new RCS file, but do
48 not deposit any revision. If the RCS file has
49 no path prefix, try to place it first into the subdirectory
50 __./RCS__, and then into the current directory. If the
51 RCS file already exists, print an error
52 message.
53
54
55 __-a__''logins''
56
57
58 Append the login names appearing in the comma-separated list
59 ''logins'' to the access list of the RCS
60 file.
61
62
63 __-A__''oldfile''
64
65
66 Append the access list of ''oldfile'' to the access list
67 of the RCS file.
68
69
70 __-e__[[''logins'']
71
72
73 Erase the login names appearing in the comma-separated list
74 ''logins'' from the access list of the RCS
75 file. If ''logins'' is omitted, erase the entire access
76 list.
77
78
79 __-b__[[''rev'']
80
81
82 Set the default branch to ''rev''. If ''rev'' is
83 omitted, the default branch is reset to the (dynamically)
84 highest branch on the trunk.
85
86
87 __-c__''string''
88
89
90 Set the comment leader to ''string''. An initial
91 __ci__, or an __rcs -i__ without __-c__, guesses
92 the comment leader from the suffix of the working
93 filename.
94
95
96 This option is obsolescent, since RCS
97 normally uses the preceding __$Log$__ line's prefix when
98 inserting log lines during checkout (see co(1)).
99 However, older versions of RCS use the
100 comment leader instead of the __$Log$__ line's prefix, so
101 if you plan to access a file with both old and new versions
102 of RCS , make sure its comment leader matches
103 its __$Log$__ line prefix.
104
105
106 __-k__''subst''
107
108
109 Set the default keyword substitution to ''subst''. The
110 effect of keyword substitution is described in co(1).
111 Giving an explicit __-k__ option to __co__,
112 __rcsdiff__, and __rcsmerge__ overrides this default.
113 Beware __rcs -kv__, because __-kv__ is incompatible
114 with __co -l__. Use __rcs -kkv__ to restore the normal
115 default keyword substitution.
116
117
118 __-l__[[''rev'']
119
120
121 Lock the revision with number ''rev''. If a branch is
122 given, lock the latest revision on that branch. If
123 ''rev'' is omitted, lock the latest revision on the
124 default branch. Locking prevents overlapping changes. If
125 someone else already holds the lock, the lock is broken as
126 with __rcs -u__ (see below).
127
128
129 __-u__[[''rev'']
130
131
132 Unlock the revision with number ''rev''. If a branch is
133 given, unlock the latest revision on that branch. If
134 ''rev'' is omitted, remove the latest lock held by the
135 caller. Normally, only the locker of a revision can unlock
136 it. Somebody else unlocking a revision breaks the lock. This
137 causes a mail message to be sent to the original locker. The
138 message contains a commentary solicited from the breaker.
139 The commentary is terminated by end-of-file or by a line
140 containing __.__ by itself.
141
142
143 __-L__
144
145
146 Set locking to ''strict''. Strict locking means that the
147 owner of an RCS file is not exempt from
148 locking for checkin. This option should be used for files
149 that are shared.
150
151
152 __-U__
153
154
155 Set locking to non-strict. Non-strict locking means that the
156 owner of a file need not lock a revision for checkin. This
157 option should ''not'' be used for files that are shared.
158 Whether default locking is strict is determined by your
159 system administrator, but it is normally
160 strict.
161
162
163 __-m__''rev''__:__''msg''
164
165
166 Replace revision ''rev'''s log message with
167 ''msg''.
168
169
170 __-M__
171
172
173 Do not send mail when breaking somebody else's lock. This
174 option is not meant for casual use; it is meant for programs
175 that warn users by other means, and invoke __rcs -u__
176 only as a low-level lock-breaking operation.
177
178
179 __-n__''name''[[__:__[[''rev'']]
180
181
182 Associate the symbolic name ''name'' with the branch or
183 revision ''rev''. Delete the symbolic name if both
184 __:__ and ''rev'' are omitted; otherwise, print an
185 error message if ''name'' is already associated with
186 another number. If ''rev'' is symbolic, it is expanded
187 before association. A ''rev'' consisting of a branch
188 number followed by a __.__ stands for the current latest
189 revision in the branch. A __:__ with an empty ''rev''
190 stands for the current latest revision on the default
191 branch, normally the trunk. For example, __rcs
192 -n__''name''__: RCS/*__ associates ''name'' with
193 the current latest revision of all the named
194 RCS files; this contrasts with __rcs
195 -n__''name''__:$ RCS/*__ which associates
196 ''name'' with the revision numbers extracted from keyword
197 strings in the corresponding working files.
198
199
200 __-N__''name''[[__:__[[''rev'']]
201
202
203 Act like __-n__, except override any previous assignment
204 of ''name''.
205
206
207 __-o__''range''
208
209
210 deletes (``outdates'') the revisions given by ''range''.
211 A range consisting of a single revision number means that
212 revision. A range consisting of a branch number means the
213 latest revision on that branch. A range of the form
214 ''rev1''__:__''rev2'' means revisions ''rev1''
215 to ''rev2'' on the same branch, __:__''rev'' means
216 from the beginning of the branch containing ''rev'' up to
217 and including ''rev'', and ''rev''__:__ means from
218 revision ''rev'' to the end of the branch containing
219 ''rev''. None of the outdated revisions can have branches
220 or locks.
221
222
223 __-q__
224
225
226 Run quietly; do not print diagnostics.
227
228
229 __-I__
230
231
232 Run interactively, even if the standard input is not a
233 terminal.
234
235
236 __-s__''state''[[__:__''rev'']
237
238
239 Set the state attribute of the revision ''rev'' to
240 ''state''. If ''rev'' is a branch number, assume the
241 latest revision on that branch. If ''rev'' is omitted,
242 assume the latest revision on the default branch. Any
243 identifier is acceptable for ''state''. A useful set of
244 states is __Exp__ (for experimental), __Stab__ (for
245 stable), and __Rel__ (for released). By default,
246 ci(1) sets the state of a revision to
247 __Exp__.
248
249
250 __-t__[[''file'']
251
252
253 Write descriptive text from the contents of the named
254 ''file'' into the RCS file, deleting the
255 existing text. The ''file'' pathname cannot begin with
256 __-__. If ''file'' is omitted, obtain the text from
257 standard input, terminated by end-of-file or by a line
258 containing __.__ by itself. Prompt for the text if
259 interaction is possible; see __-I__. With __-i__,
260 descriptive text is obtained even if __-t__ is not
261 given.
262
263
264 __-t-__''string''
265
266
267 Write descriptive text from the ''string'' into the
268 RCS file, deleting the existing
269 text.
270
271
272 __-T__
273
274
275 Preserve the modification time on the RCS
276 file unless a revision is removed. This option can suppress
277 extensive recompilation caused by a make(1)
278 dependency of some copy of the working file on the
279 RCS file. Use this option with care; it can
280 suppress recompilation even when it is needed, i.e. when a
281 change to the RCS file would mean a change to
282 keyword strings in the working file.
283
284
285 __-V__
286
287
288 Print RCS 's version number.
289
290
291 __-V__''n''
292
293
294 Emulate RCS version ''n''. See
295 co(1) for details.
296
297
298 __-x__''suffixes''
299
300
301 Use ''suffixes'' to characterize RCS
302 files. See ci(1) for details.
303
304
305 __-z__''zone''
306
307
308 Use ''zone'' as the default time zone. This option has no
309 effect; it is present for compatibility with other
310 RCS commands.
311
312
313 At least one explicit option must be given, to ensure
314 compatibility with future planned extensions to the
315 __rcs__ command.
316 !!COMPATIBILITY
317
318
319 The __-b__''rev'' option generates an
320 RCS file that cannot be parsed by
321 RCS version 3 or earlier.
322
323
324 The __-k__''subst'' options (except __-kkv__)
325 generate an RCS file that cannot be parsed by
326 RCS version 4 or earlier.
327
328
329 Use __rcs -V__''n'' to make an RCS file
330 acceptable to RCS version ''n'' by
331 discarding information that would confuse version
332 ''n''.
333
334
335 RCS version 5.5 and earlier does not support
336 the __-x__ option, and requires a __,v__ suffix on an
337 RCS pathname.
338 !!FILES
339
340
341 __rcs__ accesses files much as ci(1) does, except
342 that it uses the effective user for all accesses, it does
343 not write the working file or its directory, and it does not
344 even read the working file unless a revision number of
345 __$__ is specified.
346 !!ENVIRONMENT
347
348
349 __RCSINIT__
350
351
352 options prepended to the argument list, separated by spaces.
353 See ci(1) for details.
354 !!DIAGNOSTICS
355
356
357 The RCS pathname and the revisions outdated
358 are written to the diagnostic output. The exit status is
359 zero if and only if all operations were
360 successful.
361 !!IDENTIFICATION
362
363
364 Author: Walter F. Tichy.
365 Manual Page Revision: 5.13; Release Date: 1995/06/05.
366 Copyright 1982, 1988, 1989 Walter F. Tichy.
367 Copyright 1990, 1991, 1992, 1993, 1994, 1995 Paul
368 Eggert.
369 !!SEE ALSO
370
371
372 rcsintro(1), co(1), ci(1), ident(1), rcsclean(1),
373 rcsdiff(1), rcsmerge(1), rlog(1), rcsfile(5)
374 Walter F. Tichy, RCS --A System for Version
375 Control, ''Software--Practice ''
376 __15__, 7 (July 1985), 637-654.
377 !!BUGS
378
379
380 A catastrophe (e.g. a system crash) can cause
381 RCS to leave behind a semaphore file that
382 causes later invocations of RCS to claim that
383 the RCS file is in use. To fix this, remove
384 the semaphore file. A semaphore file's name typically begins
385 with __,__ or ends with _____.
386
387
388 The separator for revision ranges in the __-o__ option
389 used to be __-__ instead of __:__, but this leads to
390 confusion when symbolic names contain __-__. For
391 backwards compatibility __rcs -o__ still supports the old
392 __-__ separator, but it warns about this obsolete
393 use.
394
395
396 Symbolic names need not refer to existing revisions or
397 branches. For example, the __-o__ option does not remove
398 symbolic names for the outdated revisions; you must use
399 __-n__ to remove the names.
400 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.