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

Re: Betr.: Enhancement Request: Icon overlays for non-updated working copies

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Thu, 4 Aug 2011 11:46:29 +0200

On Thu, Aug 4, 2011 at 11:33, Stefan Pendl <stefan.pendl.71_at_gmail.com> wrote:
>> >
>> > It's already checking every single folder visible to see
>> whether it's a
>> > (1.7-format) working copy or not.
>>
>> Really?
>> Strange, I thought I should know this...
>>
>
> I would expect it to check only the root folder, since v1.7 does only use the root folder and has no longer a .svn/_svn folder in
> every sub-folder.
> In addition, if the root folder is v1.6 the sub-folders will be too anyways.
>
> So yes, this observation is strange ;-)

What the cache does is check every path, yes. But for pre-1.7 working
copies, it gets an error returned and immediately assumes somethings
wrong with the working copy and blocks it from getting scanned until
something inside that path changes. It won't get scanned anymore
otherwise.

What I could do however is to assume status 'obstructed' or something
like that for pre-1.7 working copies. But that's dangerous because the
overlay icon wouldn't be correct. and any status than 'none' as
assumed now for such folders means the cache will retry scanning them
often - if someone doesn't want to upgrade a working copy because it's
used by older clients, then the cache would go crazy...

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2809047
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-08-04 11:46:51 CEST

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

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