HP-UX Reference (11i v3 07/02) - 1 User Commands A-M (vol 1)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

141

142

143

144

145

146

147

148

149

150

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 ter-

minates 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 ﬁles containing lines consisting of a single period (

.).

RCS is designed to be used with text ﬁles only. Attempting to use RCS with nontext (binary) ﬁles results in

data corruption.

AUTHOR

co was developed by Walter F. Tichy.