You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Guido Anzuoni <gu...@kyneste.com> on 2005/01/19 09:00:18 UTC
Locking working copy
I have recently read a performance issue related to WC locking.
But, what is the need of locking a WC IF it is a personal,
single-threaded, workspace.
To prevent concurrent access by whom ?
Guido.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Locking working copy
Posted by Ben Collins-Sussman <su...@collab.net>.
On Jan 19, 2005, at 3:00 AM, Guido Anzuoni wrote:
> I have recently read a performance issue related to WC locking.
> But, what is the need of locking a WC IF it is a personal,
> single-threaded, workspace.
> To prevent concurrent access by whom ?
>
It's not that uncommon for users to share a working copy. For example,
a working copy may represent a semi-live 'staging' copy of a website.
N users may commit to the repository, then any of the N users might go
and run 'svn up' on the staging copy.
(A while back, when svn had bugs related to shared working copies, we
got complaints all the time.)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org