rcsdiff(1) CLIX rcsdiff(1)
NAME
rcsdiff - Compares RCS revisions
SYNOPSIS
rcsdiff [-ksubst] [-q] [-rrev1] [-rrev2] [-Vn] [-xsuffixes] [diff flags]
file ...
FLAGS
-ksubst Affects the keyword substitution when extracting revisions. (See
co(1) for more information.) For example, -kk -r1.1 -r1.2 ignores
differences in keyword values when comparing revisions 1.1 and
1.2. To avoid excess output from locker name substitution, -kkvl
is assumed if (1) at most one revision option is given, (2) no -k
flag is given, (3) -kkv is the default keyword substitution, and
(4) the working file's mode would be produced by co -l.
-q (Quiet mode.) Suppresses diagnostic output.
-r If rev1 and rev2 are omitted, rcsdiff compares the latest revision
on the default branch (normally the highest branch on the trunk)
with the contents of the corresponding working file. This is
useful for determining what was changed since the last check-in.
If rev1 is given, but rev2 is omitted, rcsdiff compares revision
rev1 of the RCS file with the contents of the corresponding
working file.
If rev1 and rev2 are given, rcsdiff compares revisions rev1 and
rev2 of the RCS file.
The revisions rev1 and rev2 may be given numerically or
symbolically, and may actually be attached to any of the flags.
-Vn Emulates RCS version n, where n may be 3, 4, or 5. This may be
useful when interchanging RCS files with others who are running
older versions of RCS. To see which version of RCS others are
running, have them use the rlog command on an RCS file; if none of
the first few lines of output contain the string branch: it is
version 3; if the dates' years have just two digits, it is
version 4; otherwise, it is version 5. An RCS file generated
while emulating version 3 will lose its default branch. An RCS
revision generated while emulating version 4 or earlier will have
a timestamp that is off by up to 13 hours. A revision extracted
while emulating version 4 or earlier will contain dates of the
form yy/mm/dd instead of yyyy/mm/dd and may also contain different
white space in the substitution for $Log$.
-x suffixes
2/94 - Intergraph Corporation 1
rcsdiff(1) CLIX rcsdiff(1)
Uses suffixes to characterize RCS files. A non-empty suffix
matches any pathname ending in the suffix. An empty suffix
matches any pathname of the form RCS/file or path/RCS/file. The
-x flag can specify a list of suffixes separated by a slash (/).
For example, -x,v/ specifies two suffixes: ,v and the empty
suffix. If two or more suffixes are specified, they are tried in
order when looking for a RCS file; the first one that works is
used for that file. If no RCS file is found but an RCS file can
be created, the suffixes are tried in order to determine the new
RCS file's name. The default for suffixes is installation-
dependent; normally it is ,v/ for hosts like UNIX that permit
commas in file names, and is empty (the empty suffix) for other
hosts.
The diff flags are all the valid flags for the diff command. All flags of
diff that apply to regular files are accepted, with the same meaning as
for diff.
DESCRIPTION
The rcsdiff command compares two revisions of each Revision Control System
(RCS) file given.
Pathnames matching an RCS suffix denote RCS files; all others denote
working files. Names are paired as explained in ci(1).
Environment Variables
The following environment variable can be useful with RCS:
RCSINIT Specifies options prepended to the argument list, separated by
spaces. A backslash escapes spaces within an option. The
RCSINIT options are prepended to the argument lists of most RCS
commands. Useful RCSINIT options include -q, -V, and -x.
EXAMPLES
The following command produces differences on the latest revision on the
default branch of RCS file f.c,v and the contents of working file f.c.
rcsdiff f.c
FILES
/tmp/,RCStxxxxxxx Temporary file.
EXIT VALUES
The exit value is 0 if there were no differences during the last
comparison, 1 if there were differences, and 2 if there were errors.
2 Intergraph Corporation - 2/94
rcsdiff(1) CLIX rcsdiff(1)
RELATED INFORMATION
Commands: ci(1), co(1), diff(1), ident(1), rcs(1), rcsclean(1),
rcsmerge(1), rlog(1)
Files: rcsfile(4)
Walter F. Tichy, ``Design, Implementation, and Evaluation of a Revision
Control System,'' in Proceedings of the 6th International Conference on
Software, IEEE, Tokyo, Sept. 1982
Walter F. Tichy, ``RCS--A System for Version Control,'' Software--
Practice & Experience, 15, 7 (July 1985), pp. 637-654.
2/94 - Intergraph Corporation 3