Blame behaving badly

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.

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

 
Received on Tue Jun 27 20:52:13 2006