Right, but might not be so uncommon having a WC as a personal workspace.
A command like
svn shared on/off PATH_TO_WC
could toggle behaviour avoiding unnecessary lock for certain (uncommon?) users.
Guido.
> -----Original Message-----
> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: Wednesday, January 19, 2005 5:04 PM
> To: Guido Anzuoni
> Cc: users@subversion.tigris.org
> Subject: Re: Locking working copy
>
>
>
> 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
Received on Wed Jan 19 18:02:03 2005