rcsdiff(1)                 DG/UX 4.30                  rcsdiff(1)



     NAME
          rcsdiff - compare RCS revisions

     SYNOPSIS
          rcsdiff [ -biwt ] [ -cefhn ] [ -rrev1 ] [ -rrev2 ] file ...

     DESCRIPTION
          Rcsdiff runs berkdiff(1) to compare two revisions of each
          RCS file given.  A file name ending in ,v is an RCS file
          name, otherwise a working file name. Rcsdiff derives the
          working file name from the RCS file name and vice versa, as
          explained in co(1).  Pairs consisting of both an RCS and a
          working file name may also be specified.

          All options except -r have the same effect as described in
          berkdiff(1).

          If both rev1 and rev2 are omitted, rcsdiff compares the
          latest revision on the trunk with the contents of the
          corresponding working file.  This is useful for determining
          what you changed since the last checkin.

          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 both rev1 and rev2 are given, rcsdiff compares revisions
          rev1 and rev2 of the RCS file.

          Both rev1 and rev2 may be given numerically or symbolically.

          The environment variable RCSDIFF controls what diff program
          rcsdiff will run.  You can set RCSDIFF to diff(1) or to
          your own alternate diff program.  If this environment
          variable is not set, berkdiff(1) will be run.

     EXAMPLES
          The command

          rcsdiff f.c

          runs berkdiff on the latest trunk revision of RCS file
          f.c,v and the contents of working file f.c.

     SEE ALSO
          ci(1), co(1), berk_diff(1), ident(1), rcs(1), rcsintro(1),
          rcsmerge(1), rlog(1), rcsfile(4).

          Walter F. Tichy, "Design, Implementation, and Evaluation of
          a Revision Control System," in Proceedings of the 6th
          International Conference on Software Engineering, IEEE,
          Tokyo, Sept. 1982.



     Licensed material--property of copyright holder(s)         Page 1