Re: svn diff - Is this behaviour expected?
From: Vincent Lefevre <vincent-svn_at_vinc17.net>
Date: Mon, 16 Aug 2010 17:17:39 +0200
On 2010-08-15 23:30:09 -0700, Bert Huijben wrote:
In my example, it wasn't a copy. But...
> In that case BASE refers to the pristine version of the copy. So no: it
What I meant is that the pristine version refers to something that
For instance, if everything is at revision 17, and you do:
svn cp foo bar
then the pristine version of both files corresponds to foo_at_17.
Then if you consider "svn diff bar", the Subversion book says:
If TARGET is a working copy path, the default behavior (when no
It is a bit ambiguous: by base, does it mean foo_at_17 or bar_at_17 ?
If a --revision option is specified in this scenario, though, it
The server compares TARGET_at_N and TARGET_at_M.
The client compares TARGET_at_N against the working copy.
That would mean for "svn diff -r17 bar", TARGET being "bar", one would
-- Vincent Lefèvre <firstname.lastname@example.org> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)Received on 2010-08-16 17:18:18 CEST
This is an archived mail posted to the Subversion Dev mailing list.