[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: bug about svn diff --summarize

From: Thomas Wicklund <tgwicklund87_at_gmail.com>
Date: Sat, 23 Aug 2014 09:58:09 -0600

On 8/22/2014 5:25 AM, Andy Levy wrote:
> On Thu, Aug 21, 2014 at 10:05 PM, ζŽηŒ›θΆ… <lmc12030218_at_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.

Received on 2014-08-23 17:58:46 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.