That was indeed the problem. I had no idea there was a cache for the
logger! I can make the entry appear/disappear by just
checking/unchecking the "Enable log caching" under settings! I think
I'll leave it disabled for now, it takes just a couple of seconds to
On Thu, 2010-08-12 at 23:28 +0100, Simon Large wrote:
> On 12 August 2010 19:39, Luis A. Montes <luis.montes_at_qdusa.com> wrote:
> > I have a problem with the log entries. I am using the latest TortoiseSVN
> > 1.6.10, Build 19898 - 32 Bit , 2010/07/16 15:46:08.
> > If I ask for the log on a particular file it does not show the latest
> > entry for that file. I see that the file is at revision 8467, but the
> > last entry on the log is for revision 8425. The repository browser
> > window shows that the latest revision is indeed 8467, but getting the
> > log from there does not work either, I still get 8425 as the latest.
> > On the other hand, if I blame the file, I do get the last version change
> > and if I now get the log from there it does show the latest.
> > I have also installed a command line svn client (from collabnet, version
> > 1.6.12-1.win32) and if I ask for the log entry on that file I do get the
> > latest.
> > I don't remember ever seeing this problem before. But one thing that I
> > did recently was I imported a medium sized (~17K revisions) Visual
> > Source Safe repository on top of my existing subversion repository, so
> > that the latest revision on the whole repository is ~25K. The dates on
> > the imported files go back ten years or more. Could be that dates going
> > back in time are confusing TortoiseSVN? This particular file was not
> > updated by the import, though.
> Try clearing the log cache.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-08-13 07:32:26 CEST