Any known issues with cached log entries?

In one of our repositories (with just under 15,000 revisions), the show
log was not showing all the revisions in a particular project trunk
folder (it was specifically missing 3 entries).

I first noticed this when I was trying to merge one of these revisions
to a different branch, and could not see it when looking at a show log
of the trunk from inside the merge procedure.

Using svn commandine log (i.e., "svn log") showed them when pointed at
the same trunk folder.

When I navigated up one folder (via repo browser) and issued a show log
from there I could see them?

Thinking I might need to experiment on the repository, I created a
completely fresh copy of the repo from a back up. However, when I did a
show log of the same the trunk folder, I could see the missing revisions
-- so it couldn't have been server side.

Normally, I only have "stop on copy/rename" checked. This had no effect
on the above behaviour, and my comparison tests had all the options the
same... so it wasn't a silly user error.

Finally, on a whim, I deleted the cache from tortoisesvn settings for
this repository. After this, when I issued a show log again, the missing
revisions have reappeared.

Has anyone else seen this before?

Should I disable log caching if I want to rely on the accuracy of the
tortoisesvn log?

Is there any info I can provide (not likely now that I have deleted the
cache and the problem has gone away)?

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3098647

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-02-13 22:34:33 CET