Home
Main website
Display Sidebar
Hide Ads
Recent Changes
View Source:
rcs(1)
Edit
PageHistory
Diff
Info
LikePages
RCS !!!RCS NAME SYNOPSIS DESCRIPTION OPTIONS COMPATIBILITY FILES ENVIRONMENT DIAGNOSTICS IDENTIFICATION SEE ALSO BUGS ---- !!NAME rcs - change RCS file attributes !!SYNOPSIS __rcs__ ''options file'' ... !!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 control attributes. For __rcs__ to work, the caller's login name must be on the access list, except if the access list is empty, the caller is the owner of the file or the superuser, or the __-i__ option is present. Pathnames matching an RCS suffix denote RCS files; all others denote working files. Names are paired as explained in ci(1). Revision numbers use the syntax described in ci(1). !!OPTIONS __-i__ Create and initialize a new RCS file, but do not deposit any revision. If the RCS file has no path prefix, try to place it first into the subdirectory __./RCS__, and then into the current directory. If the RCS file already exists, print an error message. __-a__''logins'' Append the login names appearing in the comma-separated list ''logins'' to the access list of the RCS file. __-A__''oldfile'' Append the access list of ''oldfile'' to the access list of the RCS file. __-e__[[''logins''] Erase the login names appearing in the comma-separated list ''logins'' from the access list of the RCS file. If ''logins'' is omitted, erase the entire access list. __-b__[[''rev''] Set the default branch to ''rev''. If ''rev'' is omitted, the default branch is reset to the (dynamically) highest branch on the trunk. __-c__''string'' Set the comment leader to ''string''. An initial __ci__, or an __rcs -i__ without __-c__, guesses the comment leader from the suffix of the working filename. This option is obsolescent, since RCS normally uses the preceding __$Log$__ line's prefix when inserting log lines during checkout (see co(1)). However, older versions of RCS use the comment leader instead of the __$Log$__ line's prefix, so if you plan to access a file with both old and new versions of RCS , make sure its comment leader matches its __$Log$__ line prefix. __-k__''subst'' Set the default keyword substitution to ''subst''. The effect of keyword substitution is described in co(1). Giving an explicit __-k__ option to __co__, __rcsdiff__, and __rcsmerge__ overrides this default. Beware __rcs -kv__, because __-kv__ is incompatible with __co -l__. Use __rcs -kkv__ to restore the normal default keyword substitution. __-l__[[''rev''] Lock the revision with number ''rev''. If a branch is given, lock the latest revision on that branch. If ''rev'' is omitted, lock the latest revision on the default branch. Locking prevents overlapping changes. If someone else already holds the lock, the lock is broken as with __rcs -u__ (see below). __-u__[[''rev''] Unlock the revision with number ''rev''. If a branch is given, unlock the latest revision on that branch. If ''rev'' is omitted, remove the latest lock held by the caller. Normally, only the locker of a revision can unlock it. Somebody else unlocking a revision breaks the lock. This causes a mail message to be sent to the original locker. The message contains a commentary solicited from the breaker. The commentary is terminated by end-of-file or by a line containing __.__ by itself. __-L__ Set 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__ Set 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. Whether default locking is strict is determined by your system administrator, but it is normally strict. __-m__''rev''__:__''msg'' Replace revision ''rev'''s log message with ''msg''. __-M__ Do not send mail when breaking somebody else's lock. This option is not meant for casual use; it is meant for programs that warn users by other means, and invoke __rcs -u__ only as a low-level lock-breaking operation. __-n__''name''[[__:__[[''rev'']] Associate the symbolic name ''name'' with the branch or revision ''rev''. Delete the symbolic name if both __:__ and ''rev'' are omitted; otherwise, print an error message if ''name'' is already associated with another number. If ''rev'' is symbolic, it is expanded before association. A ''rev'' consisting of a branch number followed by a __.__ stands for the current latest revision in the branch. A __:__ with an empty ''rev'' stands for the current latest revision on the default branch, normally the trunk. For example, __rcs -n__''name''__: RCS/*__ associates ''name'' with the current latest revision of all the named RCS files; this contrasts with __rcs -n__''name''__:$ RCS/*__ which associates ''name'' with the revision numbers extracted from keyword strings in the corresponding working files. __-N__''name''[[__:__[[''rev'']] Act like __-n__, except override any previous assignment of ''name''. __-o__''range'' 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 revisions ''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 can have branches or locks. __-q__ Run quietly; do not print diagnostics. __-I__ Run interactively, even if the standard input is not a terminal. __-s__''state''[[__:__''rev''] Set the state attribute of the revision ''rev'' to ''state''. If ''rev'' is a branch number, assume the latest revision on that branch. If ''rev'' is omitted, assume the latest revision on the default branch. Any identifier is acceptable for ''state''. A useful set of states is __Exp__ (for experimental), __Stab__ (for stable), and __Rel__ (for released). By default, ci(1) sets the state of a revision to __Exp__. __-t__[[''file''] Write descriptive text from the contents of the named ''file'' into the RCS file, deleting the existing text. The ''file'' pathname cannot begin with __-__. If ''file'' is omitted, obtain the text from standard input, terminated by end-of-file or by a line containing __.__ by itself. Prompt for the text if interaction is possible; see __-I__. With __-i__, descriptive text is obtained even if __-t__ is not given. __-t-__''string'' Write descriptive text from the ''string'' into the RCS file, deleting the existing text. __-T__ Preserve the modification time on the RCS file unless a revision is removed. This option can suppress extensive recompilation caused by a make(1) dependency of some copy of the working file on the RCS file. Use this option with care; it can suppress recompilation even when it is needed, i.e. when a change to the RCS file would mean a change to keyword strings in the working file. __-V__ Print RCS 's version number. __-V__''n'' Emulate RCS version ''n''. See co(1) for details. __-x__''suffixes'' Use ''suffixes'' to characterize RCS files. See ci(1) for details. __-z__''zone'' Use ''zone'' as the default time zone. This option has no effect; it is present for compatibility with other RCS commands. At least one explicit option must be given, to ensure compatibility with future planned extensions to the __rcs__ command. !!COMPATIBILITY The __-b__''rev'' option generates an RCS file that cannot be parsed by RCS version 3 or earlier. The __-k__''subst'' options (except __-kkv__) generate an RCS file that cannot be parsed by RCS version 4 or earlier. Use __rcs -V__''n'' to make an RCS file acceptable to RCS version ''n'' by discarding information that would confuse version ''n''. RCS version 5.5 and earlier does not support the __-x__ option, and requires a __,v__ suffix on an RCS pathname. !!FILES __rcs__ accesses files much as ci(1) does, except that it uses the effective user for all accesses, it does not write the working file or its directory, and it does not even read the working file unless a revision number of __$__ is specified. !!ENVIRONMENT __RCSINIT__ options prepended to the argument list, separated by spaces. See ci(1) for details. !!DIAGNOSTICS The RCS pathname and the revisions outdated are written to the diagnostic output. The exit status is zero if and only if all operations were successful. !!IDENTIFICATION Author: Walter F. Tichy. Manual Page Revision: 5.13; Release Date: 1995/06/05. Copyright 1982, 1988, 1989 Walter F. Tichy. Copyright 1990, 1991, 1992, 1993, 1994, 1995 Paul Eggert. !!SEE ALSO rcsintro(1), co(1), ci(1), ident(1), rcsclean(1), rcsdiff(1), rcsmerge(1), rlog(1), rcsfile(5) Walter F. Tichy, RCS --A System for Version Control, ''Software--Practice '' __15__, 7 (July 1985), 637-654. !!BUGS A catastrophe (e.g. a system crash) can cause RCS to leave behind a semaphore file that causes later invocations of RCS to claim that the RCS file is in use. To fix this, remove the semaphore file. A semaphore file's name typically begins with __,__ or ends with _____. The separator for revision ranges in the __-o__ option used to be __-__ instead of __:__, but this leads to confusion when symbolic names contain __-__. For backwards compatibility __rcs -o__ still supports the old __-__ separator, but it warns about this obsolete use. Symbolic names need not refer to existing revisions or branches. For example, the __-o__ option does not remove symbolic names for the outdated revisions; you must use __-n__ to remove the names. ----
12 pages link to
rcs(1)
:
rcsmerge(1)
Man1r
ci(1)
co(1)
ident(1)
rcsclean(1)
rcsdiff(1)
rcsfile(5)
rcsfreeze(1)
rcsintro(1)
rlog(1)
RCS
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.
