Next: , Up: rdiff   [Contents][Index]

A.16.1 rdiff options

These standard options are supported by rdiff (see 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).

-k kflag

Process keywords according to kflag. See Keyword substitution.


Local; don’t descend subdirectories.


Examine directories recursively. This option is on by default.

-r tag

Use revision tag.

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.

Next: , Up: rdiff   [Contents][Index]