Re: Any CVS tricks for creating patch files?

[Larry Jones]

Spiro Trikaliotis writes:
> 
> Ok, I just tested it, you are right. Well, I looked at the documentation
> (info cvs, the online manual) but could not find it documented anywhere
> that -N is always assumed with rdiff. Isn't that a "documentation hole"?

Given that rdiff doesn't even *have* a -N option, what would you have
the documentation say?!?  It already says that it creates a patch to
"bring an old release up-to-date with the new release" --  creating
files that didn't previously exist is obviously an essential part of
that process.  You'll notice that rdiff (aka patch) hardly has any of
the regular diff options -- that's because most of them aren't really
options for patches, they're either required or not valid.  Perhaps we
should consider splitting patch and rdiff into separate commands on the
feature branch: patch would continue to have the current behavior, rdiff
would provide all the usual diff options.

-Larry Jones

Oh, now don't YOU start on me. -- Calvin