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

Re: Exclusive Locking: 2nd draft

From: Snow <snowl_at_snow.vg>
Date: 2004-05-20 20:36:24 CEST

Ben Collins-Sussman wrote:
> Great discussion, folks. Allow me to take back the microphone and
> create a new, simpler proposal based on yesterday's threads.
> I'm now in the camp with ghudson and jpieper: I don't think we need
> special "lock-txns" at all. It's a bunch of unnecessary complexity.
> All we need is a lock table that describes which paths are locked by
> whom.
> Use case #1: svn client
> LOCK -----> path cannot be locked or committed by anyone else.

What about directory locks? Does locking /trunk prevent anyone from locking
or commiting /trunk/svn/file1.txt? Similarly does locking
/trunk/svn/file1.txt prevent anyone from locking /trunk?

> GET -----> returns path@HEAD universally. existence of lock is
> irrelevant.
> commit ----> allowed on path IFF you own the lock.

Can't you commit if noone owns the lock?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 20 20:43:08 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.