1CI(1) General Commands Manual CI(1)
2
6 ci - check in RCS revisions
7
9 ci [options] file ...
10
12 ci stores new revisions into RCS files. Each pathname matching an RCS
13 suffix is taken to be an RCS file. All others are assumed to be work‐
14 ing files containing new revisions. ci deposits the contents of each
15 working file into the corresponding RCS file. If only a working file
16 is given, ci tries to find the corresponding RCS file in an RCS subdi‐
17 rectory and then in the working file's directory. For more details,
18 see FILE NAMING below.
19 For ci to work, the caller's login must be on the access list, except
21 if the access list is empty or the caller is the superuser or the owner
22 of the file. To append a new revision to an existing branch, the tip
23 revision on that branch must be locked by the caller. Otherwise, only
24 a new branch can be created. This restriction is not enforced for the
25 owner of the file if non-strict locking is used (see rcs(1)). A lock
26 held by someone else can be broken with the rcs command.
27 Unless the -f option is given, ci checks whether the revision to be
29 deposited differs from the preceding one. If not, instead of creating
30 a new revision ci reverts to the preceding one. To revert, ordinary ci
31 removes the working file and any lock; ci -l keeps and ci -u removes
32 any lock, and then they both generate a new working file much as if
33 co -l or co -u had been applied to the preceding revision. When
34 reverting, any -n and -s options apply to the preceding revision.
35 For each revision deposited, ci prompts for a log message. The log
37 message should summarize the change and must be terminated by end-of-
38 file or by a line containing . by itself. If several files are checked
39 in ci asks whether to reuse the previous log message. If the standard
40 input is not a terminal, ci suppresses the prompt and uses the same log
41 message for all files. See also -m.
42 If the RCS file does not exist, ci creates it and deposits the contents
44 of the working file as the initial revision (default number: 1.1). The
45 access list is initialized to empty. Instead of the log message, ci
46 requests descriptive text (see -t below).
47 The number rev of the deposited revision can be given by any of the
49 options -f, -i, -I, -j, -k, -l, -M, -q, -r, or -u. rev can be sym‐
50 bolic, numeric, or mixed. Symbolic names in rev must already be
51 defined; see the -n and -N options for assigning names during checkin.
52 If rev is $, ci determines the revision number from keyword values in
53 the working file.
54 If rev begins with a period, then the default branch (normally the
56 trunk) is prepended to it. If rev is a branch number followed by a
57 period, then the latest revision on that branch is used.
58 If rev is a revision number, it must be higher than the latest one on
60 the branch to which rev belongs, or must start a new branch.
61 If rev is a branch rather than a revision number, the new revision is
63 appended to that branch. The level number is obtained by incrementing
64 the tip revision number of that branch. If rev indicates a non-exist‐
65 ing branch, that branch is created with the initial revision numbered
66 rev.1.
67 If rev is omitted, ci tries to derive the new revision number from the
69 caller's last lock. If the caller has locked the tip revision of a
70 branch, the new revision is appended to that branch. The new revision
71 number is obtained by incrementing the tip revision number. If the
72 caller locked a non-tip revision, a new branch is started at that revi‐
73 sion by incrementing the highest branch number at that revision. The
74 default initial branch and level numbers are 1.
75 If rev is omitted and the caller has no lock, but owns the file and
77 locking is not set to strict, then the revision is appended to the
78 default branch (normally the trunk; see the -b option of rcs(1)).
79 Exception: On the trunk, revisions can be appended to the end, but not
81 inserted.
82
84 -rrev Check in revision rev.
85 -r The bare -r option (without any revision) has an unusual meaning
87 in ci. With other RCS commands, a bare -r option specifies the
88 most recent revision on the default branch, but with ci, a bare
89 -r option reestablishes the default behavior of releasing a lock
90 and removing the working file, and is used to override any
91 default -l or -u options established by shell aliases or
92 scripts.
93 -l[rev]
95 works like -r, except it performs an additional co -l for the
96 deposited revision. Thus, the deposited revision is immediately
97 checked out again and locked. This is useful for saving a revi‐
98 sion although one wants to continue editing it after the
99 checkin.
100 -u[rev]
102 works like -l, except that the deposited revision is not locked.
103 This lets one read the working file immediately after checkin.
104 The -l, bare -r, and -u options are mutually exclusive and
106 silently override each other. For example, ci -u -r is equiva‐
107 lent to ci -r because bare -r overrides -u.
108 -f[rev]
110 forces a deposit; the new revision is deposited even it is not
111 different from the preceding one.
112 -k[rev]
114 searches the working file for keyword values to determine its
115 revision number, creation date, state, and author (see co(1)),
116 and assigns these values to the deposited revision, rather than
117 computing them locally. It also generates a default login mes‐
118 sage noting the login of the caller and the actual checkin date.
119 This option is useful for software distribution. A revision
120 that is sent to several sites should be checked in with the -k
121 option at these sites to preserve the original number, date,
122 author, and state. The extracted keyword values and the default
123 log message can be overridden with the options -d, -m, -s, -w,
124 and any option that carries a revision number.
125 -q[rev]
127 quiet mode; diagnostic output is not printed. A revision that
128 is not different from the preceding one is not deposited, unless
129 -f is given.
130 -i[rev]
132 initial checkin; report an error if the RCS file already exists.
133 This avoids race conditions in certain applications.
134 -j[rev]
136 just checkin and do not initialize; report an error if the RCS
137 file does not already exist.
138 -I[rev]
140 interactive mode; the user is prompted and questioned even if
141 the standard input is not a terminal.
142 -d[date]
144 uses date for the checkin date and time. The date is specified
145 in free format as explained in co(1). This is useful for lying
146 about the checkin date, and for -k if no date is available. If
147 date is empty, the working file's time of last modification is
148 used.
149 -M[rev]
151 Set the modification time on any new working file to be the date
152 of the retrieved revision. For example, ci -d -M -u f does not
153 alter f's modification time, even if f's contents change due to
154 keyword substitution. Use this option with care; it can confuse
155 make(1).
156 -mmsg uses the string msg as the log message for all revisions checked
158 in. By convention, log messages that start with # are comments
159 and are ignored by programs like GNU Emacs's vc package. Also,
160 log messages that start with {clumpname} (followed by white
161 space) are meant to be clumped together if possible, even if
162 they are associated with different files; the {clumpname} label
163 is used only for clumping, and is not considered to be part of
164 the log message itself.
165 -nname assigns the symbolic name name to the number of the checked-in
167 revision. ci prints an error message if name is already
168 assigned to another number.
169 -Nname same as -n, except that it overrides a previous assignment of
171 name.
172 -sstate
174 sets the state of the checked-in revision to the identifier
175 state. The default state is Exp.
176 -tfile writes descriptive text from the contents of the named file into
178 the RCS file, deleting the existing text. The file cannot begin
179 with -.
180 -t-string
182 Write descriptive text from the string into the RCS file, delet‐
183 ing the existing text.
184 The -t option, in both its forms, has effect only during an ini‐
186 tial checkin; it is silently ignored otherwise.
187 During the initial checkin, if -t is not given, ci obtains the
189 text from standard input, terminated by end-of-file or by a line
190 containing . by itself. The user is prompted for the text if
191 interaction is possible; see -I.
192 For backward compatibility with older versions of RCS, a bare -t
194 option is ignored.
195 -T Set the RCS file's modification time to the new revision's time
197 if the former precedes the latter and there is a new revision;
198 preserve the RCS file's modification time otherwise. If you
199 have locked a revision, ci usually updates the RCS file's modi‐
200 fication time to the current time, because the lock is stored in
201 the RCS file and removing the lock requires changing the RCS
202 file. This can create an RCS file newer than the working file
203 in one of two ways: first, ci -M can create a working file with
204 a date before the current time; second, when reverting to the
205 previous revision the RCS file can change while the working file
206 remains unchanged. These two cases can cause excessive recompi‐
207 lation caused by a make(1) dependency of the working file on the
208 RCS file. The -T option inhibits this recompilation by lying
209 about the RCS file's date. Use this option with care; it can
210 suppress recompilation even when a checkin of one working file
211 should affect another working file associated with the same RCS
212 file. For example, suppose the RCS file's time is 01:00, the
213 (changed) working file's time is 02:00, some other copy of the
214 working file has a time of 03:00, and the current time is 04:00.
215 Then ci -d -T sets the RCS file's time to 02:00 instead of the
216 usual 04:00; this causes make(1) to think (incorrectly) that the
217 other copy is newer than the RCS file.
218 -wlogin
220 uses login for the author field of the deposited revision. Use‐
221 ful for lying about the author, and for -k if no author is
222 available.
223 -V Print RCS's version number.
225 -Vn Emulate RCS version n. See co(1) for details.
227 -xsuffixes
229 specifies the suffixes for RCS files. A nonempty suffix matches
230 any pathname ending in the suffix. An empty suffix matches any
231 pathname of the form RCS/path or path1/RCS/path2. The -x option
232 can specify a list of suffixes separated by /. For example,
233 -x,v/ specifies two suffixes: ,v and the empty suffix. If two
234 or more suffixes are specified, they are tried in order when
235 looking for an RCS file; the first one that works is used for
236 that file. If no RCS file is found but an RCS file can be cre‐
237 ated, the suffixes are tried in order to determine the new RCS
238 file's name. The default for suffixes is installation-depen‐
239 dent; normally it is ,v/ for hosts like Unix that permit commas
240 in filenames, and is empty (i.e. just the empty suffix) for
241 other hosts.
242 -zzone specifies the date output format in keyword substitution, and
244 specifies the default time zone for date in the -ddate option.
245 The zone should be empty, a numeric UTC offset, or the special
246 string LT for local time. The default is an empty zone, which
247 uses the traditional RCS format of UTC without any time zone
248 indication and with slashes separating the parts of the date;
249 otherwise, times are output in ISO 8601 format with time zone
250 indication. For example, if local time is January 11, 1990, 8pm
251 Pacific Standard Time, eight hours west of UTC, then the time is
252 output as follows:
253 option time output
255 -z 1990/01/12 04:00:00 (default)
256 -zLT 1990-01-11 20:00:00-08
257 -z+05:30 1990-01-12 09:30:00+05:30
258 The -z option does not affect dates stored in RCS files, which
260 are always UTC.
261
263 Pairs of RCS files and working files can be specified in three ways
264 (see also the example section).
265 1) Both the RCS file and the working file are given. The RCS pathname
267 is of the form path1/workfileX and the working pathname is of the form
268 path2/workfile where path1/ and path2/ are (possibly different or
269 empty) paths, workfile is a filename, and X is an RCS suffix. If X is
270 empty, path1/ must start with RCS/ or must contain /RCS/.
271 2) Only the RCS file is given. Then the working file is created in the
273 current directory and its name is derived from the name of the RCS file
274 by removing path1/ and the suffix X.
275 3) Only the working file is given. Then ci considers each RCS suffix X
277 in turn, looking for an RCS file of the form path2/RCS/workfileX or (if
278 the former is not found and X is nonempty) path2/workfileX.
279 If the RCS file is specified without a path in 1) and 2), ci looks for
281 the RCS file first in the directory ./RCS and then in the current
282 directory.
283 ci reports an error if an attempt to open an RCS file fails for an
285 unusual reason, even if the RCS file's pathname is just one of several
286 possibilities. For example, to suppress use of RCS commands in a
287 directory d, create a regular file named d/RCS so that casual attempts
288 to use RCS commands in d fail because d/RCS is not a directory.
289
291 Suppose ,v is an RCS suffix and the current directory contains a subdi‐
292 rectory RCS with an RCS file io.c,v. Then each of the following com‐
293 mands check in a copy of io.c into RCS/io.c,v as the latest revision,
294 removing io.c.
295 ci io.c; ci RCS/io.c,v; ci io.c,v;
297 ci io.c RCS/io.c,v; ci io.c io.c,v;
298 ci RCS/io.c,v io.c; ci io.c,v io.c;
299 Suppose instead that the empty suffix is an RCS suffix and the current
301 directory contains a subdirectory RCS with an RCS file io.c. The each
302 of the following commands checks in a new revision.
303 ci io.c; ci RCS/io.c;
305 ci io.c RCS/io.c;
306 ci RCS/io.c io.c;
307
309 An RCS file created by ci inherits the read and execute permissions
310 from the working file. If the RCS file exists already, ci preserves
311 its read and execute permissions. ci always turns off all write per‐
312 missions of RCS files.
313
315 Temporary files are created in the directory containing the working
316 file, and also in the temporary directory (see TMPDIR under ENVIRON‐
317 MENT). A semaphore file or files are created in the directory contain‐
318 ing the RCS file. With a nonempty suffix, the semaphore names begin
319 with the first character of the suffix; therefore, do not specify an
320 suffix whose first character could be that of a working filename. With
321 an empty suffix, the semaphore names end with _ so working filenames
322 should not end in _.
323 ci never changes an RCS or working file. Normally, ci unlinks the file
325 and creates a new one; but instead of breaking a chain of one or more
326 symbolic links to an RCS file, it unlinks the destination file instead.
327 Therefore, ci breaks any hard or symbolic links to any working file it
328 changes; and hard links to RCS files are ineffective, but symbolic
329 links to RCS files are preserved.
330 The effective user must be able to search and write the directory con‐
332 taining the RCS file. Normally, the real user must be able to read the
333 RCS and working files and to search and write the directory containing
334 the working file; however, some older hosts cannot easily switch
335 between real and effective users, so on these hosts the effective user
336 is used for all accesses. The effective user is the same as the real
337 user unless your copies of ci and co have setuid privileges. As
338 described in the next section, these privileges yield extra security if
339 the effective user owns all RCS files and directories, and if only the
340 effective user can write RCS directories.
341 Users can control access to RCS files by setting the permissions of the
343 directory containing the files; only users with write access to the
344 directory can use RCS commands to change its RCS files. For example,
345 in hosts that allow a user to belong to several groups, one can make a
346 group's RCS directories writable to that group only. This approach
347 suffices for informal projects, but it means that any group member can
348 arbitrarily change the group's RCS files, and can even remove them
349 entirely. Hence more formal projects sometimes distinguish between an
350 RCS administrator, who can change the RCS files at will, and other
351 project members, who can check in new revisions but cannot otherwise
352 change the RCS files.
353
355 To prevent anybody but their RCS administrator from deleting revisions,
356 a set of users can employ setuid privileges as follows.
357 · Check that the host supports RCS setuid use. Consult a trustworthy
359 expert if there are any doubts. It is best if the seteuid system
360 call works as described in Posix 1003.1a Draft 5, because RCS can
361 switch back and forth easily between real and effective users, even
362 if the real user is root. If not, the second best is if the setuid
363 system call supports saved setuid (the {_POSIX_SAVED_IDS} behavior of
364 Posix 1003.1-1990); this fails only if the real or effective user is
365 root. If RCS detects any failure in setuid, it quits immediately.
366 · Choose a user A to serve as RCS administrator for the set of users.
368 Only A can invoke the rcs command on the users' RCS files. A should
369 not be root or any other user with special powers. Mutually suspi‐
370 cious sets of users should use different administrators.
371 · Choose a pathname B to be a directory of files to be executed by the
373 users.
374 · Have A set up B to contain copies of ci and co that are setuid to A
376 by copying the commands from their standard installation directory D
377 as follows:
378 mkdir B
380 cp D/c[io] B
381 chmod go-w,u+s B/c[io]
382 · Have each user prepend B to their path as follows:
384 PATH=B:$PATH; export PATH # ordinary shell
386 set path=(B $path) # C shell
387 · Have A create each RCS directory R with write access only to A as
389 follows:
390 mkdir R
392 chmod go-w R
393 · If you want to let only certain users read the RCS files, put the
395 users into a group G, and have A further protect the RCS directory as
396 follows:
397 chgrp G R
399 chmod g-w,o-rwx R
400 · Have A copy old RCS files (if any) into R, to ensure that A owns
402 them.
403 · An RCS file's access list limits who can check in and lock revisions.
405 The default access list is empty, which grants checkin access to any‐
406 one who can read the RCS file. If you want limit checkin access,
407 have A invoke rcs -a on the file; see rcs(1). In particular,
408 rcs -e -aA limits access to just A.
409 · Have A initialize any new RCS files with rcs -i before initial
411 checkin, adding the -a option if you want to limit checkin access.
412 · Give setuid privileges only to ci, co, and rcsclean; do not give them
414 to rcs or to any other command.
415 · Do not use other setuid commands to invoke RCS commands; setuid is
417 trickier than you think!
418
420 RCSINIT
421 options prepended to the argument list, separated by spaces. A
422 backslash escapes spaces within an option. The RCSINIT options
423 are prepended to the argument lists of most RCS commands. Use‐
424 ful RCSINIT options include -q, -V, -x, and -z.
425 TMPDIR Name of the temporary directory. If not set, the environment
427 variables TMP and TEMP are inspected instead and the first value
428 found is taken; if none of them are set, a host-dependent
429 default is used, typically /tmp.
430
432 For each revision, ci prints the RCS file, the working file, and the
433 number of both the deposited and the preceding revision. The exit sta‐
434 tus is zero if and only if all operations were successful.
435
437 Author: Walter F. Tichy.
438 Manual Page Revision: 5.17; Release Date: 1995/06/16.
439 Copyright © 1982, 1988, 1989 Walter F. Tichy.
440 Copyright © 1990, 1991, 1992, 1993, 1994, 1995 Paul Eggert.
441
443 co(1), emacs(1), ident(1), make(1), rcs(1), rcsclean(1), rcsdiff(1),
444 rcsintro(1), rcsmerge(1), rlog(1), setuid(2), rcsfile(5)
445 Walter F. Tichy, RCS--A System for Version Control, Software--Practice
446 & Experience 15, 7 (July 1985), 637-654.
447GNU 1995/06/16 CI(1)