bug about svn diff --summarize

[李猛超 <lm...@163.com>]

Hello:


    If I have a file at version 1. then I modefy and commit it, get version 2, Now I make the file be same as version 1 and commit, get version 3.
    Running "svn diff -r 1", I will get no changes, but "svn diff -r 1 --summarize" will get the file is modefied.


Best wishes,


                                                                                                                                                                                           Marco Li

Re: bug about svn diff --summarize

[Thomas Wicklund <tg...@gmail.com>]

On 8/22/2014 5:25 AM, Andy Levy wrote:
> On Thu, Aug 21, 2014 at 10:05 PM, 李猛超 <lm...@163.com> wrote:
>> Hello:
>>
>>      If I have a file at version 1. then I modefy and commit it, get version
>> 2, Now I make the file be same as version 1 and commit, get version 3.
>>      Running "svn diff -r 1", I will get no changes, but "svn diff -r 1
>> --summarize" will get the file is modefied.
> That's exactly how it's supposed to work. The file *did* change
> between r1 & r3 (the log says so), but the contents were eventually
> the same again (a diff shows no net change). --summarize doesn't
> calculate a full diff of every file between those 2 revisions, AFAIK.

I know there's been some discussion of this the last few months, but my 
experience is that with SVN 1.8 diff functionality changed. I use the 
options "--diff-cmd diff -x -q" instead of --summarize (the scripts were 
written before --summarize was added to "svn diff"). Under SVN 1.7 I 
would only see files with different contents (or properties). With 1.8 
files with the same contents which are not identical in the repository 
show up as different. This is particularly true of binary files.

Tom

Re: bug about svn diff --summarize

[Thomas Wicklund <tg...@gmail.com>]

On 8/22/2014 5:25 AM, Andy Levy wrote:
> On Thu, Aug 21, 2014 at 10:05 PM, 李猛超 <lm...@163.com> wrote:
>> Hello:
>>
>>      If I have a file at version 1. then I modefy and commit it, get version
>> 2, Now I make the file be same as version 1 and commit, get version 3.
>>      Running "svn diff -r 1", I will get no changes, but "svn diff -r 1
>> --summarize" will get the file is modefied.
> That's exactly how it's supposed to work. The file *did* change
> between r1 & r3 (the log says so), but the contents were eventually
> the same again (a diff shows no net change). --summarize doesn't
> calculate a full diff of every file between those 2 revisions, AFAIK.

I know there's been some discussion of this the last few months, but my 
experience is that with SVN 1.8 diff functionality changed. I use the 
options "--diff-cmd diff -x -q" instead of --summarize (the scripts were 
written before --summarize was added to "svn diff"). Under SVN 1.7 I 
would only see files with different contents (or properties). With 1.8 
files with the same contents which are not identical in the repository 
show up as different. This is particularly true of binary files.

Tom

Re: bug about svn diff --summarize

[Andy Levy <an...@gmail.com>]

On Thu, Aug 21, 2014 at 10:05 PM, 李猛超 <lm...@163.com> wrote:
> Hello:
>
>     If I have a file at version 1. then I modefy and commit it, get version
> 2, Now I make the file be same as version 1 and commit, get version 3.
>     Running "svn diff -r 1", I will get no changes, but "svn diff -r 1
> --summarize" will get the file is modefied.

That's exactly how it's supposed to work. The file *did* change
between r1 & r3 (the log says so), but the contents were eventually
the same again (a diff shows no net change). --summarize doesn't
calculate a full diff of every file between those 2 revisions, AFAIK.