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

Re: Log Cache problem on a branch doesn't show latest revision

From: Lübbe Onken <luebbe.tortoisesvn_at_googlemail.com>
Date: Fri, 11 Sep 2009 15:04:20 +0200

Hi Stefan Fuhrmann:
you wrote:

> I suspect that the skip ranges mark the (missing) HEAD
> revision as 'not relevant for that path', so the repository
> query will either start with a much smaller revision number
> or stop above it.

OK, but how does that fit with the TortoiseSVN versions that I've been
running over the past two weeks?

 From a previous post:
>> On the 25.8.2009 I installed TortoiseSVN r16974 over r16670
>> On the 4.9.2009 I installed TortoiseSVN r17111 over r16974
>> On the 10.9.2010 I installed TortoiseSVN r17148 over r17111

The commits to the branch show up correctly in the log for all commits
made with TSVN r16974 and before. They are wrong for TSVN r17111 and
after. Is this just a coincidence? Was I lucky that the cache did get
updated? I rarely use the revision graph, so chances that I updated the
log cache this way are pretty slim. Yesterday I committed another bugfix
to that branch and it didn't show up either.

> Could you do a new export with the latest nightly and
> send me the *.skipranges.csv? It is grouped (not sorted)
> by path.

Zipped file attached. It contains two skip ranges files. One *before*
showing the log for the repository root and one *after*, which kind of
repairs the log cache.

I think the culprit is in the following rows of the *before* file:
2076,"/branches/ProjectA-Release",5753,1
2076,"/branches/ProjectA-Release",5756,4
2076,"/branches/ProjectA-Release",5762,2
2076,"/branches/ProjectA-Release",5777,1
2076,"/branches/ProjectA-Release",5812,1
2076,"/branches/ProjectA-Release",5819,4
2076,"/branches/ProjectA-Release",5831,9

the skip ranges 5753-5812 look ok to me, because the skipped revisions
are really not part of that branch. 5819,4 excludes r5821 and 5831,9
excludes 5833 which were merged from trunk.

The log for the branch is shown up to (and including) r5806 *before*.
One thing worries me a bit. If 5831,9 means that nine revisions starting
from r5831 are skipped, this can't be correct, because the highest
revision number in the repo is currently r5834. OTOH r5833 is shown on
the branch *after* the cache has been updated.

Cheers&thanks
- Lübbe

--
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net  PGP Key ID 0x23F511AB
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2393599
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].

Received on 2009-09-11 15:04:30 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.