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

Re: Blame behaving badly

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-06-28 09:42:01 CEST

On 6/27/06, Loren Osborn <lsosborn@dis-sol-inc.com> wrote:
> 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.

You can, but not directly from the working copy:
* start the repository browser
* switch to the requested revision
* right-click on the file, choose "blame"

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

Already done in trunk.

> Thank you for any input you may have,

The reason you get that error message is because the path actually
*does not exist* in the revision range you want to blame. And in the
1.3.x API there's no way to specify a peg revision to tell Subversion
where to look first for the path.
In 1.4.x, this is fixed.


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Jun 28 11:18: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.