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

Re: Include / Exclude Path woes Was: TSVNCache and Handles on USB Dri ve

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-12-18 21:38:23 CET

Lübbe Onken wrote:
> Hi Stefan,
>
> You wrote:
>> On 12/18/06, Lübbe Onken <l.onken@rac.de> wrote:
>>> You wrote:
>>>> What exactly are those patterns used for again?
>>>> Oh, yes: to tell the cache which folders to scan so it doesn't have
>>>> to scan everything just to find out whether something is versioned
>>>> or not.
> [*1]
>
>>> Is there any specific reason why you chose to ignore the second half
>>> of my posting? I think that following the 'svn st -v' logic is a
>>> good way to tell the cache what is versioned and what's not.
>> I thought it was clear after my answer:
>
> Not it wasn't. Even your sarcasm[*1] was completely wasted, because I wanted
> an answer *why* you are doing it this way and not *what* it is actually
> doing / supposed to do.

I'm sorry, but you suggested to just include the *versioned* folders
recursively. That's why I answered that way. After all, you should know
better than most people here how the cache works.

>> it doesn't matter. The cache gets change notifications not in the
>> 'right' order (from top down) but in random order (whenever a change
>> to a file is done). That means it can get a change notification for a
>> file somewhere in an unversioned folder way before it has fetched the
>> status of the versioned parent folder.
>
> Now that's a proper answer :) It could have saved us five e-mails and an
> hour or two of thinking and researching if you would have given it earlier.

I'm surprised that I had to explain that to you. Think about it: how
many times have I already explained the very same on this list? And it's
not as if you just joined this list.

> If I understand it correcly, the cache doesn't really know whether a folder
> is versioned or not. It relies on patterns defined by the user to match
> paths that get thrown at it by Windows. These paths currently act as a
> sieve.
>
> I think I also now understand why I have to enter "Include C:\Delphi
> C:\Delphi\*" to get proper overlays on C:\Delphi and its subfolders.
> "C:\Delphi" is an exact match and in fact excludes all subfolders of
> "C:\Delphi" which then have to be added again with "C:\Delphi\*". This is
> not intuitive.

You could also just use "C:\Delphi*" instead of two include folders. But
then also the any unversioned folder (e.g. C:\Delphi\output) will be
included and the cache will try to crawl those if a file gets changed
inside those folders.

I'm sorry if I'm a little bit cranky. I'm trying to prepare for the
upcoming holidays by eating less (don't worry, I'll eat more soon). And
being hungry makes me cranky. So expect a lot of sarcastic comments from
me this week, and of course again after the holidays :)

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Dec 18 21:38:34 2006

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