Re: [Subclipse-users] bug: Compare With > Base Revision stops working after a rename

Hi

I know thats how the __storage__ model works, but the __mental__ model
is still "its the same file, just in a different place".
From the users perspective, it's still a "move" operation, and the file
is connected with its ancestor.

So when I do a "Compare With -> Base Revision", what I'm really saying
is "Compare the current file with it's immediate ancestor".

And from that perspective, the current operation is not particularly
friendly.

BTW, similar problems show up when browsing the history of moved files
in subclipse, and attempting to view old revisions.

Thanks, Noel

Mark Phippard wrote:
> On 8/8/07, Noel Grandin <noel@peralex.com> wrote:
>
>
>> If I rename a class, and then attempt to do Right Click File -> Compare
>> With -> Base Revision, the right hand side of the compare window is blank.
>>
>
> When you rename something, Subversion internally does a copy. So
> essentially, it is like a newly added file and is treated as such.
> Subversion just adds the special treatment on commit that is connected
> with the history of the file it came from.
>
>

Disclaimer: http://www.peralex.com/disclaimer.html
Received on Wed Aug 8 17:21:03 2007