[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Any CVS tricks for creating patch files?

From: Spiro Trikaliotis
Subject: Re: Any CVS tricks for creating patch files?
Date: Thu, 10 Jun 2004 10:54:16 +0200
User-agent: Mutt/1.5.6i

Hello Larry,

* On Wed, Jun 09, 2004 at 04:12:47PM -0400 Larry Jones wrote:
> Given that rdiff doesn't even *have* a -N option, what would you have
> the documentation say?!? 

I don't know what others think about it, but I assume that a command
"cvs rXXX" is just a function like "cvs XXX", but I do not need a
working sandbox to do it.

I have never thought that this could not be true. In fact, I did not
even know that there is also a "cvs patch".

> 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.

Obviously, yes.

> 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.

Well, now that I know the difference between rdiff and diff, I have no
problems. In fact, rdiff -u or diff -uN is exactly what I need.

My only concern is that other people might be confused like I was.

For me, there is no need to change the rdiff behaviour. Now, for me, it
is not even essential to change to docu on rdiff, but there might be new
users which might like that one.


Spiro R. Trikaliotis

reply via email to

[Prev in Thread] Current Thread [Next in Thread]