c

co(1)

co(1)

Access Control Lists (ACLs)

Optional ACL entries should not be added to RCS ®les because they might be deleted.

DIAGNOSTICS

The RCS ®le name, the working ®le name, and the revision number retrieved are written to the diagnostic output. The exit status always refers to the last ®le 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 ®le 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 ®le foo.c,v:

co -r1.1 foo.c,v

Check out version 1.1 of RCS ®le foo.c,v to the standard output:

co -p1.1 foo.c,v

Check out the version of ®le foo.c,v that existed on September 18, 1992:

co -d"09/18/92" foo.c,v

WARNINGS

The co command generates the working ®le name by removing the ,v from the end of the RCS ®le name. If the given RCS ®le name is too long for the ®le system on which the RCS ®le 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 -doption gets confused in some circumstances, and accepts no date before 1970.

The -joption does not work for ®les containing lines consisting of a single . .

RCS is designed to be used with text ®les only. Attempting to use RCS with non-text (binary) ®les 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), rcs®le(4), acl(5), rcsintro(5).

Section 1−100

− 3 −

HP-UX Release 11i: December 2000