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

svn blame -g gets wrong commit numbers

From: Brazhnik <brazhnik_at_gmail.com>
Date: Tue, 17 Feb 2009 18:43:50 +0300

Hello.

I found a wrong behavior of tortoiseSVN blame command in some my files.

Further investigation has shown that it seems the problem in 'svn
blame -g' command.

The same problem is in some files of svn.collab.net/repos/svn/trunk.
For example in subversion/svn/main.c

Step for reproduce:

0. svn version is 1.5.5 (windows XP pro / Vista home prem)

1. execute
svn blame -r 35734
http://svn.collab.net/repos/svn/trunk/subversion/svn/main.c >main.b

2. execute
svn blame -g -r 35734
http://svn.collab.net/repos/svn/trunk/subversion/svn/main.c >main.b-g

3. see line 327 of main.b: last changes in commit 18522. ('svn diff'
confirmed this)
   see line 327 of main.b-g: last changes in commit 1 !!!

4. see line 937 of main.b: last changes in commit 31487.
   see line 937 of main.b: last changes in commit 31715!!! how can
original (from merge info) commit number may be greater than direct
commit number?

----
I checked those steps using svn.exe form tortoisesvn night build
TortoiseSVN-1.5.99.15383-dev-win32-svn-1.6.0-dev.msi
with the same strange results.
I am worry about svn 1.6
Thanks,
--
Andrey
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1179481
Received on 2009-02-17 16:44:13 CET

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