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

Re: Locking on svn.collab.net (was svn.collab.net Subversion upgraded to 1.2.0-rc1)

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-04-08 16:12:12 CEST

On Apr 7, 2005, at 4:55 PM, C. Michael Pilato wrote:

> "C. Michael Pilato" <cmpilato@collab.net> writes:
>
>> May the locking begin.
>
> On second thought, I've disabled locking on the server until the
> committers vote in support of enabling it.
>
> To start the voting process, I'll register a -0.9 until mailer.py
> learns
> to send lock and unlock notifications.
>

I'm not sure what you're afraid of here. Yes, locking is "on" by
default in 1.2, but it also has no teeth by default -- anyone can
break/steal locks.

AFAICT, our own community of developers has no real need or interest in
locking at all. If any of us used it, it would be purely for
experimentation and testing. And if it turns out that a lock *was* in
the way of a commit, anyone could easily break it.

So I don't really see a "threat" to our normal processes here, only an
opportunity for testing. I don't see the need for coming up with
complex HACKING policies about it, or the need to vote to enable
something so harmless.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 8 16:14:14 2005

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