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

Blame behaving badly

From: Loren Osborn <lsosborn_at_dis-sol-inc.com>
Date: 2006-06-27 21:22:28 CEST

I discovered a problem with "blame" (and a few other tools, but "blame" is the most annoying as I use it most often).  When I request a "blame" on a file up to a revision prior to the file being moved / copied to its current location.  To reproduce this issue:

1) Create a file in an SVN repository
2) Modify the file a few times to give it some history... let's say this takes us to revision 123
3) Make some SWEEPING change (like running the code through a pretty printer) that changes almost every line in the file.  We'll call this revision 124
4) Further modify the file a times to give it a bit more history... let's say this takes us to revision 234
5) Use the tortoise equivalent of "svn mv" to more the file to a new location within the repository, preserving its history. i.e. revision 235
6) Further modify the file a times to give it a bit more history in its new location... let's say this takes us to revision 345 aka. HEAD
7) Now run blame on the file through "HEAD" or 345... everything works as expected.
8) Run blame on the file through 235... everything STILL works as expected.
9) Now lets say we want to see a "blame" on changes BEFORE revision 124 ... our blame "brick wall": So we try to run blame only through revision 123...
a. ERROR... can't find file... because the file wasn't *IN* that location at that time
10) In fact we can't view any blame prior to 235 because that's when the file appeared in its current location.

Likewise, it would be nice to have "Blame" in the context sensitive menu from the show log window once it is working properly.

So.... official bug report:
Ref: http://tortoisesvn.sourceforge.net/node/54

        1) This bug was reproduced on TortoiseSVN 1.3.5 this morning.
        2) I have too many looming deadlines to be "stuck" with a potentially unstable "nightly builds" version of TortoiseSVN right now... sorry
        3) I Searched the mailing list, and FlySpray... found nothing relevant.
        4) Nettiquite: been doing mailing lists for a while...
        5) Affected platform: MS WinXP Pro ver 2002 + Service Pack 2 on a 2.6 GHz Celeron with 0.5 GB RAM... Subversion server running on IBM Power architecture over http connection
        6) details:
                a) Bug reproduction instructions above...
                b) I expected to get a blame report
                c) I got a path not found dialog.

Hope this helps.

Thank you for any input you may have,

Loren Osborn
Software Engineer
Dispensing Solutions Inc.
(714) 437-0330
3000 West Warner Ave.
Santa Ana, CA  92704

To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Jun 27 21:22:55 2006

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

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