Re: finishing `svn diff': two ways to do it

Matt Kraai <kraai@alumni.carnegiemellon.edu> writes:
> So `svn diff foo.c' and `svn diff -r 17 foo.c' produce a patch
> which, when applied to revision 17, would transform it into the
> working copy, whereas `svn diff -r 20 foo.c' and
> `svn diff -r 5 foo.c' produce patches that would transform the
> working copy into revision 20 and revision 5, respectively?
>
> This seems needlessly bizarre. Why not follow CVS, which always
> produces a patch which changes into the working copy when zero or
> one revision is specified?

Yup; I just had it backwards, see my response just now to Greg Hudson.
I agree, let's default the same way CVS does.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:44 2006