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

Re: [TSVN] Re: still buggy

From: Molle Bestefich <molle.bestefich_at_gmail.com>
Date: 2005-03-27 12:26:49 CEST

>>> And no: making the shell check each file first would result in a
>>> severe performance degradation!
>>
>> Just to check the file/folder you right-click on?
>
> People complaint that right-clicking on a file/folder inside a working
> copy takes way too long (if the wc is big). So we changed it so that the
> status is fetched from the cache too if you right-click.

Nonetheless:

1. The bug as described in the issue tracker is not fixed. It should
be reopened. No point in closing a perfectly valid bug description.
Remove it from the 1.1.4 milestone if you think it's not important
that it be fixed now (I think the milestone needs an update anyway?).

2. Ok. I'll throw some ideas around, there's got to be a way to fix.
 How about this:
Whenever a refresh (F5) occurs, don't make an entire treewalk.
Instead, for each item that is found to have an entry in the cache:
 - Check that it has a .svn folder. If it doesn't, remove it from the
cache (or set a 'needs_update' mark on the item in the cache..
whatever's fastest) and skip applying the overlay
 - Check the timestamp on the ".svn/entries" file (applies for all
files that's being checked) or the "<wc folder>/.svn/entries" file
(applies for all folders that's being checked). Compare it with a
cached value. If the timestamp has changed, the item needs to be
refreshed. To avoid the treewalk delay, set a needs_update flag on
the item in the cache scheduling it for a refresh and just return a
blank overlay on the item for now.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Mar 27 12:27:21 2005

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.