Re: "svn diff -c" behavior on file copy from an old revision
From: Vincent Lefevre <vincent-svn_at_vinc17.net>
Date: Thu, 21 Nov 2019 15:09:05 +0100
On 2019-11-20 15:21:22 +0100, Johan Corveleyn wrote:
I think that, as -c is documented, this is the same issue: "-c M" is a
svn diff -c3 file2
is equivalent to
svn diff -r2:3 file2_at_BASE
Here, BASE is assumed to be 3 (or equivalent). Thus one should get the
svn cat -r2 file2_at_3
svn cat -r3 file2_at_3
> Indeed, in r2 there was no file2.
This is not really what is described here:
OPERATIVE-REV is older than PEG-REV. Thus
1. Locate item in the revision identified by PEG-REV. There can be
→ This is file2.
2. Trace the object's history backwards (through any possible renames)
→ As I understand it, the history is as followed.
There is file2 at revision 3, which is a copy of file1 from revision 1.
> In r1 there was a predecessor of file2_at_3, namely file1_at_1. You could
Exactly, but the reason is not that file1 was unchanged in r2.
> But what if file1 would have been changed in r2 (yet file2_at_3 was a
Obviously file1_at_1, as file1_at_2 is *not* an ancestor of file2_at_3.
Remember, we are looking at the (backward) *history* of file2_at_3.
> Or what if file1 was deleted in r2?
> I guess the same questions can be asked for 'svn diff -c 3' (what if
My above interpretation of the history would have the advantage to
-- Vincent Lefèvre <email@example.com> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)Received on 2019-11-21 15:09:23 CET
This is an archived mail posted to the Subversion Users mailing list.