Stefan Küng wrote:
> Robert Roessler wrote:
>> Mike Dixon wrote:
>>> ...
>>> I also tested the drive type exclusion while I was at it, and that has
>>> the same problem; if I set it up like this:
>>> -drive types-
>>> None.
>>>
>>> -include-
>>> E:\trunk*
>>>
>>> -exclude-
>>> (empty)
>>>
>>> , it results in the same behavior: E:\trunk does not get overlays, but
>>> its children do.
>>>
>>> So I guess my question is: is this a bug or a feature? :) I'm assuming
>>> it's a bug, but the help should be updated if this is intended behavior.
>>
>> My setup on a 1.6.2 nightly from last week is SIMILAR to yours (but not
>> the same), and WORKS exactly as I expect.
>>
>> In terms of your filesystem, I would have
>>
>> drive types = none (like yours)
>> include = e:\trunk\* (different)
>> exclude = * (different)
>>
>> I have been using this setup for numerous releases to good effect - note
>> that this should give overlays for E:\trunk itself as well as its
>> children (but nowhere else in your entire filesystem).
>
> There was a change so that the included drive types now have a lower
> priority. The change was necessary so that included drive types could
> still be excluded without ever even accessing them (performance problems
> with network drives and flaky connections).
>
> To include a folder, you have to specify
> E:\trunk\
> E:\trunk\*
With the 16624 nightly build on Vista SP2 x64, I see no change - the
configuration I describe above continues to work exactly as I expect -
the "E:\trunk\" include entry is not needed.
"E:\trunk\*" gives icon overlays for all of the folders in the "trunk"
directory, as well as for their contents... but if it ever stops
working, I suppose I will know what to try. ;)
Robert Roessler
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2364616
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-06-23 20:35:42 CEST