Next: rdiff examples, Up: rdiff [Contents][Index]
These standard options are supported by rdiff
(see Common options for a complete description of
them):
-D dateUse the most recent revision no later than date.
-fIf no matching revision is found, retrieve the most recent revision (instead of ignoring the file).
-k kflagProcess keywords according to kflag. See Keyword substitution.
-lLocal; don’t descend subdirectories.
-RExamine directories recursively. This option is on by default.
-r tagUse revision tag.
In addition to the above, these options are available:
-cUse the context diff format. This is the default format.
-sCreate 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.
-tA 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.
-uUse 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 vnExpand 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.
Next: rdiff examples, Up: rdiff [Contents][Index]