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

Re: 1.6 vs. 1.8: strange behavior of 'svn diff -cN WC-FILE' if the file was created in rev N by copying

From: Tobias Bading <tbading_at_web.de>
Date: Tue, 25 Jun 2013 20:33:18 +0200

On 25.06.2013, at 20:08, Peter Samuelson wrote:
> [Tobias Bading]
>> Seriously though, what would you have to do if you have the path of a
>> FILE in the working copy and a revision number N and you would like
>> to know what was changed in that file in that revision?
>
> Something like this:
>
> $ LC_ALL=C svn log -v -l1 new_foo
> ------------------------------------------------------------------------
> r6 | peters | 2013-06-25 13:05:16 -0500 (Tue, 25 Jun 2013) | 1 line
> Changed paths:
> A /new_foo (from /foo:1)
>
> Copied and modified foo_at_1 to new_foo.
> ------------------------------------------------------------------------
>
> Parse the "A" line, then use that information to construct a diff
> command line. Either of the following will work:
>
> svn diff -r1:6 new_foo
> svn diff ^/foo_at_1 ^/new_foo_at_6
>
> Peter

I think I can already hear Emacs developers of both VC camps, the Bazaar'ians and the Git'ians, laughing together in harmony in the distance... ;-)
No disrespect & thank you for the hint, but shouldn't a version control system be able to answer the question "what's changed?" without making you jump through hoops?

Tobias
Received on 2013-06-25 20:33:58 CEST

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