Stefan Küng wrote:
> Peter McNab wrote:
>
>> Maybe not so bad after all.
>>
>> I did not have the TSVNCacheWindow enabled in the registry on the XP
>> box so could not see what was going on behind the scenes.
>> Enabled said window.
>> Repeated virtually the same commit on an up to date branch instead of
>> Trunk.
>> Keeping in mind I use Executive Software's Recovery bin
>> Noticed a lot of crawling of the recovery bin folders as replaced
>> files were added during commit. (.svn folder replaced files?)
>> Left F5 well alone.
>> Everything updated as required, delayed only by crawling of the
>> recovery bin area.
>>
>> Seems like it would be good if the cache could be taught to ignore
>> certain folders, and for me to do more testing before posting too.
>
>
> The cache already prioritizes notifications from the directory watcher
> over crawl requests from other places. So this shouldn't really be
> that big of an issue.
> But I just found something which might have something to do with what
> you experienced. Maybe you can try again with a build > 5176.
>
> Stefan
>
r5153 on XP is behaving very much like the cache of old in that I'm
seeing lots of the invalidating messages in the TSVNCacheWindow while
locally deleting a WC and then when it's checked out again. No chance
the build is from old code is there?
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Dec 17 16:31:29 2005