rcs(1) rcs(1)NAME rcs - change RCS file attributes SYNOPSIS rcs [-i] [-alogins]] [-Aoldfile] [-e[logins]] [-cstring] [-l[rev]] [-u[rev]] [-L] [-U] [-nname[:rev]] [-Nname[:rev]] [-orange] [-q] [-sstate[:rev]] [-t[txtfile]] files DESCRIPTION rcs creates new RCS files or changes attributes of existing ones. An RCS file contains multiple revisions of text, an access list, a change log, descriptive text, and some con- trol attributes. For rcs to work, the caller's login name must be on the access list, unless the access list is empty, the caller is the owner of the file or the superuser, or the -i option is present. Files ending in ,v are RCS files, and all others are working files. If a working file is given, rcs tries to find the corresponding RCS file, first in directory ./RCS and then in the current directory, as explained in co(1). -i Creates and initializes a new RCS file, but does not deposit any revision. If the RCS file has no path prefix, rcs tries to place it, first into the subdirectory ./RCS and then into the current directory. If the RCS file already exists, an error message is printed. -alogins Appends the login names appearing in the comma- separated list logins to the access list of the RCS file. -Aoldfile Appends the access list of oldfile to the access list of the RCS file. -e[logins] Erases the login names appearing in the comma- separated list logins from the access list of the RCS file. If logins is omitted, the entire ac- cess list is erased. -cstring Sets the comment leader to string. The comment leader is printed before every log-message line generated by the keyword $Log$ during checkout (see co). This is useful for programming languages without multiline comments. During rcs -i or initial ci, the comment leader is guessed from the suffix of the working file. -l[rev] Locks the revision with number rev. If a branch is given, the latest revision on that branch is locked. If rev is omitted, the latest revision April, 1990 1
rcs(1) rcs(1)on the trunk is locked. Locking prevents over- lapping changes. A lock is removed with ci or rcs -u. -u[rev] Unlocks the revision with number rev. If a branch is given, the latest revision on that branch is unlocked. If rev is omitted, the la- test lock held by the caller is removed. Normal- ly, only the locker of a revision may unlock it. Anyone else unlocking a revision breaks the lock. This causes a mail message to be sent to the ori- ginal locker. The message contains a commentary solicited from the breaker. The commentary is terminated with a line containing a single . or CONTROL-D. -L Sets locking to strict. Strict locking means that the owner of an RCS file is not exempt from locking for checkin. This option should be used for files that are shared. -U Sets locking to non-strict. Non-strict locking means that the owner of a file need not lock a revision for checkin. This option should not be used for files that are shared. The default (-L or -U) is determined by your system administra- tor. -nname[:rev] Associates the symbolic name name with the branch or revision rev. rcs prints an error message if name is already associated with another number. If rev is omitted, the symbolic name is deleted. -Nname[:rev] Same as -n, except that it overrides a previous assignment of name. -orange Deletes (outdates) the revisions given by range. A range consisting of a single revision number means that revision. A range consisting of a branch number means the latest revision on that branch. A range of the form rev1-rev2 means re- visions rev1 to rev2 on the same branch, -rev means from the beginning of the branch containing rev up to and including rev, and rev- means from revision rev to the end of the branch containing rev. None of the outdated revisions may have branches or locks. -q Quiet mode; diagnostics are not printed. 2 April, 1990
rcs(1) rcs(1)-sstate[:rev] Sets the state attribute of the revision rev to state. If rev is omitted, the latest revision on the trunk is assumed. If rev is a branch number, the latest revision on that branch is assumed. Any identifier is acceptable for state. A useful set of states is Exp (for experimental), Stab (for stable), and Rel (for released). By de- fault, ci sets the state of a revision to Exp. -t[txtfile] Writes descriptive text into the RCS file and deletes the existing text. If txtfile is omit- ted, rcs prompts the user for text supplied from the standard input, terminated with a line con- taining a single . or CONTROL-D. Otherwise, the descriptive text is copied from the file txtfile. If the -i option is present, descriptive text is requested even if -t is not given. The prompt is suppressed if the standard input is not a termi- nal. DIAGNOSTICS The RCS filename and the revisions outdated are written to the diagnostic output. The exit status always refers to the last RCS file operated upon, and is 0 if the operation was successful, 1 if otherwise. FILES The caller of the command must have read/write permission for the directory containing the RCS file and read permis- sion for the RCS file itself. rcs creates a semaphore file in the same directory as the RCS file to prevent simultane- ous update. For changes, rcs always creates a new file. On successful completion, rcs deletes the old one and renames the new one. This strategy makes links to RCS files use- less. DISCLAIMER This reference manual entry describes a utility that Apple understands to have been released into the public domain by its author or authors. Apple has included this public domain utility for your convenience. Use it at your own discretion. Often the source code can be obtained if addi- tional requirements are met, such as the purchase of a site license from an author or institution. IDENTIFICATION Author: Walter F. Tichy, Purdue University, West Lafayette, IN 47907.cCopyright 1982 by Walter F. Tichy.April, 1990 3
rcs(1) rcs(1)SEE ALSO ci(1), co(1), ident(1), rcsdiff(1), rcsintro(1), rcsmerge(1), rlog(1), rcsfile(4), sccstorcs(1M). Walter F. Tichy, ``Design, Implementation, and Evaluation of a Revision Control System,'' in Proceedings of the 6th International Conference on Software Engineering, IEEE, Tok- yo, September 1982. 4 April, 1990