1.6.1 svn blame -g gets wrong commit numbers

Hello,
some weeks ago I wrote about "blame -g" problem.
http://subversion.tigris.org/ds/viewMessage.do?dsMessageId=1120874&dsForumId=1065
http://subversion.tigris.org/ds/viewMessage.do?dsMessageId=1134733&dsForumId=1065

Now we have subversion 1.6.1 with the same wrong behavior.
But this post has no answers from svn developers.

Do you trust to svn blame? I do not and it is very sad.

--
Andrey
On Tue, Feb 17, 2009 at 7:43 PM, Brazhnik <brazhnik_at_gmail.com> wrote:
> 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
>
> Steps 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-g: 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=1065&dsMessageId=1715925
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].