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

Re: [TSVN] Too much recursion going on in TSVN?

From: SteveKing <stefankueng_at_gmail.com>
Date: 2004-10-28 12:03:08 CEST

On Thu, 28 Oct 2004 12:03:12 +0200, Amir Kolsky <amir@xpandsoft.com> wrote:
> I am wondering if maybe tortoise is addressing the problem from the wrong
> angle...

Not really.

> There are several scenarios that might cause the status of a subtree to
> change (i.e., the status of an entity inside the tree):
> File changes as a result of an update, an operation within Tortoise and an
> operation outside of Tortoise, e.g., inside visual studio - directly or
> indirectly.
> Then there's the issue of svn:properties changing.
> I do not know how the properties are implemented, but the NTFS file system
> will allow tortoise to be aware of any changes in the .svn directories via
> reparse points. This means that any change to any of the folders can be
> caught be toirtoise an propagated up the folder heirarchy without the need
> to recursively scan the folder heirarchy.
> The reason this will work is that once a change is detected there is no need
> to access the remote repository but only the local base, which remains
> constant between updates...
> In esseence this means that Tortoise will switch to Push rather than Pull...

That would require to write a service which runs constantly in the
background, watching the filesystem for changes. This would slow down
the whole system, even if you're not browsing the filesystem with the
explorer but all the time!


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Oct 28 13:07:44 2004

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.