Log Caching problem

Hi Folks,

I think I have discovered a problem in the log caching which is related to
copied/renamed files/folders. This is a follow-up to my previous post:
'Endless loop in blame, possible bug in log caching?'

We have a repository at work that has undergone a major restructuring in
revisions 970-976 (a lot of directories have been moved around). Current
revision is ~3000.

If I show the log of a file/folder with 'stop on copy/rename' set,
TortoiseSVN fetches all the logs from 976-HEAD and displays them fine. The
status line tells me '93 revisions from 976-2992'.

When I uncheck 'stop on copy/rename' with the log-dialog still open,
TortoiseSVN tries to fetch the missing seven revisions to fill up 100. It
doesn't visibly loop, but it doesn't terminate either. When I press abort,
the seven revisions 858-974 (with gaps in between of course) are repeated
many times in the log dialog.

When I then click on 'show all' I get a looping progress bar at the bottom.
I have to abort again. The lowest revision shown in the log is 353, which is
the revision in which the file was created. Needless to say that the
revisions < 976 are repeated over and over again.

The behaviour observed when running blame is IMO just a result of this
behaviour. When I blame from 976-HEAD everything is ok. When I blame from
974 to HEAD, Blame crashes (report sent). When I blame from 858 to head,
Blame doesn't terminate.

Hope that helps in debugging.

Cheers
- Lübbe

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org