> -----Original Message-----
> From: Vincent Lefevre [mailto:vincent-...@vinc17.net]
> Sent: zondag 15 augustus 2010 16:50
> To: dev@subversion.apache.org
> Subject: Re: svn diff - Is this behaviour expected?
>
> On 2010-08-15 05:34:08 -0700, Bert Huijben wrote:
> > > Conversely, when blah has been added, but not committed,
> > >
> > > svn diff -rBASE blah
> > >
> > > gives a diff instead of an error (indeed an error is expected because
> > > b...@base doesn't exist, as this can been seen with "svn cat blah").
> >
> > If I remember correctly comparing to BASE does not compare to the
> version in
> > the repository, but to the local pristine version. Just like not
providing
> > -rBASE. (Compare it to -r<revision of base>).
>
> ??? I've never said anything different. I think you missed the point
> that there is no local pristine version here, since "blah" hasn't
> been committed yet.
>
> BTW, the local pristine version does correspond to some revision
> in the repository. It shouldn't be mixed up with the working copy
> version.
What if the file is a copy?
In that case BASE refers to the pristine version of the copy. So no: it
doesn't refer to just a revision.
Bert
