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

RE: Re: no overlays visible in working copy under Program Files directory

From: Peter Mounce <Peter.Mounce_at_whitbybird.com>
Date: 2006-02-13 14:36:24 CET

> -----Original Message-----
> From: Roel Harbers [mailto:roel@roelharbers.com]

> I agree, since I only have 2 locations where I have working copies.
> It would be even better to be able to only *include* folders
> you know contain working copies.

+1 from me. I have the same (roughly) setup of only a few places that
have WCs.

How about a treeview in the TSVN config (a new cache-config page?) of
[tristate checkbox] - directoryname
* ticked = this directory and all sub-directories get crawled
* unticked = this directory and all sub-directories don't get crawled
* third-state = this directory has contents to be crawled, but not
necessarily all sub-directories.

The roots are each system hard drive, which, by default first install,
are all checked. The user is told to go into the config to set up which
directories he wants crawled. It might be possible to get the installer
to include a dialog where the user can pick initial settings for this.

Checking out to a directory should update the crawl settings to include
the WC's parent directory (based on a new tickbox on the checkout dialog
that's ticked by default?). Adding a directory like this should not add
unversioned directories to the crawl? So it would add a third-state
setting here? Something like that?

Is there a way to detect when the last WC in a crawled directory is
deleted, and remove that directory's entry from the crawl settings at
that point?

(Our systems are down at the moment, and you know what they say about
idle thumbs making work...)


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Feb 13 14:36:53 2006

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.