On Nov 23, 2004, at 11:03 AM, Philip Martin wrote:
> Branko Čibej <brane@xbc.nu> writes:
>
>> I'm trying think of a good reason why we'd support any kind of
>> concurrent operation in the WC. If we just serialised everything, "svn
>> st" and friends could do this cleanup themselves.
>
> How about a GUI that runs status periodically (or in response to some
> sort of filesystem notification system), that could cause concurrent
> operation with some other process running, say, update. If status
> takes a write lock the update might fail with an "already locked"
> error, but when the user investigated there would be no lock.
>
As a matter of fact, this is what the next version of sc-plugin
(TortoiseSVN for Mac OSX Finder) is probably going to do. I've been
working with the author, and he's planning to write an optional
background daemon that periodically runs 'svn status' on directories of
your choice... so that when you visit the working copy, the
icon-overlays have already been pre-computed.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 23 18:11:49 2004