You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Brazhnik <br...@gmail.com> on 2009/04/14 20:47:44 UTC
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 <br...@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@subversion.tigris.org].
Re: 1.6.1 svn blame -g gets wrong commit numbers
Posted by Lieven Govaerts <sv...@mobsol.be>.
> On Tue, Feb 17, 2009 at 7:43 PM, Brazhnik<br...@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'm not sure if the issue you're seeing in the svn repository is a bug
in 'svn blame' or rather a problem with the mergeinfo in our repo.
If you take a revision before r33229 instead of HEAD:
$ svn blame -g -r 33228
http://svn.collab.net/repos/svn/trunk/subversion/svn/main.c
... the output is alright.
lgo@lgo-laptop:~/dev/trunk$ svn diff -c 33229 -N
..
Property changes on: .
___________________________________________________________________
Modified: svn:mergeinfo
Reverse-merged /trunk:r1-28216
Merged /branches/file-externals:r31705-33228
I don't think that 'Reversed-merged' line is correct, but don't know
enough of the merge-tracking internals to be sure.
Lieven
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1808372
1.6.1 svn blame -g gets wrong commit numbers
Posted by Brazhnik <br...@gmail.com>.
Hello,
some weeks ago I wrote about "blame -g" problem.
users@subversion:
http://subversion.tigris.org/ds/viewMessage.do?dsMessageId=1120874&dsForumId=1065
http://subversion.tigris.org/ds/viewMessage.do?dsMessageId=1134733&dsForumId=1065
dev@subversion:
http://subversion.tigris.org/ds/viewMessage.do?dsMessageId=1179481&dsForumId=462
Now we have subversion 1.6.1 with the same wrong behavior.
But those posts have no answers from svn developers.
It is very sad if I cannot trust to svn blame.
--
Andrey
On Tue, Feb 17, 2009 at 7:43 PM, Brazhnik <br...@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=462&dsMessageId=1765416