|
|
1.1 root 1: .TH SCCSTORCS 8 "29 June 1983"
2: .UC 4
3: .SH NAME
4: sccstorcs \- build RCS file from SCCS file
5: .SH SYNOPSIS
6: \fBsccstorcs\fR [\fB\-t\fR] [\fB\-v\fR] \fIs.file\fR ...
7: .SH DESCRIPTION
8: .I Sccstorcs
9: builds an RCS file from each SCCS file argument.
10: The deltas and comments for each delta are preserved and installed into
11: the new RCS file in order.
12: Also preserved are
13: the user access list and descriptive text, if any,
14: from the SCCS file.
15: .PP
16: The following flags are meaningful:
17: .TP
18: \fB\-t\fR
19: Trace only.
20: Prints detailed information about the SCCS file and lists the
21: commands that would be executed to produce the RCS file.
22: No commands are actually executed and no RCS file is made.
23: .TP
24: \fB\-v\fR
25: Verbose.
26: Prints each command that is run while it is building the RCS file.
27: .SH FILES
28: For each s.\fIsomefile\fR,
29: .I Sccstorcs
30: writes the files \fIsomefile\fR and \fIsomefile\fR,v
31: which should not already exist.
32: .I Sccstorcs
33: will abort, rather than overwrite those files if they do exist.
34: .SH SEE ALSO
35: ci (1), co (1), rcs (1).
36: .br
37: Walter F. Tichy, "Design, Implementation, and Evaluation of a Revision
38: Control System," in \fIProceedings of the 6th International Conference
39: on Software Engineering\fR, IEEE, Tokyo, Sept. 1982.
40: .SH DIAGNOSTICS
41: All diagnostics are written to stderr.
42: Non-zero exit status on error.
43: .SH BUGS
44: .I Sccstorcs
45: does not preserve all SCCS options specified in the SCCS file.
46: Most notably, it does not preserve removed deltas, MR numbers,
47: and cutoff points.
48: .SH AUTHOR
49: Ken Greer
50:
51: Copyright \(co 1983 by Kenneth L. Greer
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.