( rdiff options

Info Catalog ( rdiff ( rdiff examples
 A.17.1 rdiff options
 These standard options are supported by `rdiff' ( Common
 options, for a complete description of them):
 `-D DATE'
      Use the most recent revision no later than DATE.
      If no matching revision is found, retrieve the most recent
      revision (instead of ignoring the file).
      Local; don't descend subdirectories.
      Examine directories recursively.  This option is on by default.
 `-r TAG'
      Use the revision specified by TAG, or when DATE is specified and
      TAG is a branch tag, the version from the branch TAG as it existed
      on DATE.  See  Common options.
    In addition to the above, these options are available:
      Use the context diff format.  This is the default format.
      Create a summary change report instead of a patch.  The summary
      includes information about files that were changed or added
      between the releases.  It is sent to the standard output device.
      This is useful for finding out, for example, which files have
      changed between two dates or revisions.
      A diff of the top two revisions is sent to the standard output
      device.  This is most useful for seeing what the last change to a
      file was.
      Use the unidiff format for the context diffs.  Remember that old
      versions of the `patch' program can't handle the unidiff format,
      so if you plan to post this patch to the net you should probably
      not use `-u'.
 `-V VN'
      Expand keywords according to the rules current in RCS version VN
      (the expansion format changed with RCS version 5).  Note that this
      option is no longer accepted.  CVS will always expand keywords the
      way that RCS version 5 does.
Info Catalog ( rdiff ( rdiff examples
automatically generated byinfo2html