[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-12 18:18:23 CEST

On Apr 11, 2005, at 6:55 PM, Justin Erenkrantz wrote:

> --On Friday, April 8, 2005 9:12 AM -0500 Ben Collins-Sussman
> <sussman@collab.net> wrote:
>
>> 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.
>
> -1 (vote, not veto) on using locks on Subversion's repository.
>
> I don't like encouraging locks to begin with on this sort of project.
> I haven't seen any justifications yet as to why anyone actively
> involved in Subversion would want to hold locks on our codebase.

I gave a justification in my mail: so we can experiment with our own
dog food. That's a tangible benefit. I then proceeded to explain why
there's no risk to leaving this door open.

Yet when I read your mail, it looks much the same as cmpilato's: I see
some sort of hatred of locks, or some perceived danger/annoyance, with
no explanation. Can we have a rational debate, other than just blind
voting?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 12 18:25:23 2005

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