Seth Woolley's Man Viewer

rcs(1) - rcs - change RCS file attributes - man 1 rcs

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

RCS(1)                                                                  RCS(1)



NAME
       rcs - change RCS file(1,n) attributes

SYNOPSIS
       rcs options file(1,n) ...

DESCRIPTION
       rcs  creates  new RCS files or changes attributes of existing ones.  An
       RCS file(1,n) contains multiple revisions of text, an access(2,5) list, a  change
       log,  descriptive  text, and some control attributes.  For rcs to work,
       the caller's login(1,3,5) name must be on  the  access(2,5)  list,  except  if(3,n)  the
       access(2,5)  list is empty, the caller is the owner of the file(1,n) or the supe-
       ruser, 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(1,8) ci(1).  Revision num-
       bers use the syntax described in(1,8) ci(1).

OPTIONS
       -i     Create and initialize a new RCS file(1,n), but  do  not  deposit  any
              revision.   If  the RCS file(1,n) has no path prefix, try to place it
              first into the subdirectory ./RCS, and  then  into  the  current
              directory.   If the RCS file(1,n) already exists, print an error(8,n) mes-
              sage.

       -alogins
              Append the login(1,3,5) names appearing  in(1,8)  the  comma-separated  list
              logins to the access(2,5) list of the RCS file.

       -Aoldfile
              Append  the access(2,5) list of oldfile to the access(2,5) list of the RCS
              file.

       -e[logins]
              Erase the login(1,3,5) names  appearing  in(1,8)  the  comma-separated  list
              logins from the access(2,5) list of the RCS file.  If logins is omit-
              ted, erase the entire access(2,5) list.

       -b[rev]
              Set the default branch to rev.  If rev is omitted,  the  default
              branch  is  reset(1,7,1 tput)  to  the  (dynamically)  highest branch on the
              trunk.

       -cstring(3,n)
              Set the comment leader to string(3,n).  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  preced-
              ing $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(3,n) you plan to
              access(2,5) a file(1,n) with both old and new versions of RCS,  make  sure
              its comment leader matches its $Log$ line prefix.

       -ksubst
              Set  the  default  keyword substitution to subst.  The effect of
              keyword substitution is described in(1,8) 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 over-
              lapping 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(1,8) 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(1,n) 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(1,n)  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 adminis-
              trator, but it is normally strict.

       -mrev:msg
              Replace revision rev's log message with msg.

       -M     Do not send(2,n) mail(1,8)  when  breaking  somebody  else's  lock.   This
              option  is  not  meant  for casual use; it is meant for programs
              that warn users(1,5) by other means, and invoke rcs -u only as a low-
              level lock-breaking operation.

       -nname[:[rev]]
              Associate  the  symbolic  name  name with the branch or revision
              rev.  Delete the symbolic name if(3,n) both : and  rev  are  omitted;
              otherwise,  print an error(8,n) message if(3,n) 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(1,8)  the  branch.   A  :
              with  an empty rev stands for the current latest revision on the
              default   branch,   normally   the    trunk.     For    example,
              rcs -nname: RCS/*  associates name with the current latest revi-
              sion  of  all  the  named(5,8)  RCS  files;   this   contrasts   with
              rcs -nname:$ RCS/*  which associates name with the revision num-
              bers extracted from keyword strings in(1,8) the corresponding working
              files.

       -Nname[:[rev]]
              Act like -n, except override any previous assignment of name.

       -orange
              deletes ("outdates") the revisions given by range.  A range con-
              sisting 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(3,n) the standard input is not a terminal.

       -sstate[: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(7,n,1 builtins)
              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(1,n)]
              Write  descriptive text from the contents of the named(5,8) file(1,n) into
              the RCS file(1,n), deleting the existing  text.   The  file(1,n)  pathname
              cannot  begin  with -.  If file(1,n) is omitted, obtain the text from
              standard input, terminated by end-of-file or by a line  contain-
              ing  . by  itself.  Prompt for the text if(3,n) interaction is possi-
              ble; see -I.  With -i, descriptive text is obtained even  if(3,n)  -t
              is not given.

       -t-string(3,n)
              Write descriptive text from the string(3,n) into the RCS file(1,n), delet-
              ing the existing text.

       -T     Preserve the modification time(1,2,n) on the RCS file(1,n) unless a revision
              is  removed.   This  option can suppress extensive recompilation
              caused by a make(1) dependency of some copy of the working  file(1,n)
              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(1,n)  would mean a change to keyword strings in(1,8) the working
              file.

       -V     Print RCS's version(1,3,5) number.

       -Vn    Emulate RCS version(1,3,5) n.  See co(1) for details.

       -xsuffixes
              Use suffixes to characterize RCS files.  See ci(1) for  details.

       -zzone Use  zone  as the default time(1,2,n) 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  -brev  option  generates  an RCS file(1,n) that cannot be parsed by RCS
       version(1,3,5) 3 or earlier.

       The -ksubst options (except -kkv) generate an RCS file(1,n) that  cannot  be
       parsed by RCS version(1,3,5) 4 or earlier.

       Use rcs -Vn to make an RCS file(1,n) acceptable to RCS version(1,3,5) n by discard-
       ing information that would confuse version(1,3,5) n.

       RCS version(1,3,5) 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 effec-
       tive user for all accesses, it does not write(1,2) the working file(1,n)  or  its
       directory, and it does not even read(2,n,1 builtins) the working file(1,n) 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 diagnos-
       tic output.  The exit(3,n,1 builtins) status is zero if(3,n) and only if(3,n) 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
       & Experience 15, 7 (July 1985), 637-654.

BUGS
       A  catastrophe  (e.g.  a  system crash) can cause RCS to leave behind a
       semaphore file(1,n) that causes later invocations of RCS to claim  that  the
       RCS  file(1,n)  is in(1,8) use.  To fix this, remove the semaphore file.  A sema-
       phore file(1,n)'s name typically begins with , or ends with _.

       The separator for revision ranges in(1,8) 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.



GNU                               1995/06/05                            RCS(1)

References for this manual (incoming links)