HP-UX Reference (11i v1 05/09) - 1 User Commands A-M (vol 1)

c
co(1) co(1)
Access Control Lists (ACLs)
Optional ACL entries should not be added to
RCS files because they might be deleted.
DIAGNOSTICS
The
RCS file name, the working file name, and the revision number retrieved are written to the diagnostic
output. The exit status always refers to the last file checked out, and is 0 if the operation was successful, 1
if unsuccessful.
EXAMPLES
Assume the current directory contains a subdirectory named
RCS with an RCS file named io.c,v. Each
of the following commands retrieves the latest revision from
RCS/io.c,v and stores it into io.c:
co io.c
co RCS/io.c,v
co io.c,v
co io.c RCS/io.c,v
co io.c io.c,v
co RCS/io.c,v io.c
co io.c,v io.c
Check out version 1.1 of RCS file foo.c,v:
co -r1.1 foo.c,v
Check out version 1.1 of RCS file foo.c,v to the standard output:
co -p1.1 foo.c,v
Check out the version of file foo.c,v that existed on September 18, 1992:
co -d"09/18/92" foo.c,v
WARNINGS
The co command generates the working file name by removing the ,v from the end of the
RCS file name.
If the given
RCS file name is too long for the file system on which the
RCS file should reside, co terminates
with an error message.
There is no way to suppress the expansion of keywords, except by writing them differently. In
nroff and
troff, this is done by embedding the null-character
\& into the keyword.
The
-d option gets confused in some circumstances, and accepts no date before 1970.
The -j option does not work for files containing lines consisting of a single .
.
RCS is designed to be used with text files only. Attempting to use RCS with non-text (binary) files results in
data corruption.
AUTHOR
co was developed by Walter F. Tichy.
SEE ALSO
ci(1), ident(1), rcs(1), rcsdiff(1), rcsmerge(1), rlog(1), rcsfile(4), acl(5), rcsintro(5).
Section 1−−100 Hewlett-Packard Company − 3 − HP-UX 11i Version 1: September 2005