[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: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-04-12 18:39:09 CEST

Ben Collins-Sussman <sussman@collab.net> writes:

> 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?

Hatred of locks? Oh, please.

Perceived danger? Er. No.

Perceived annoyance? Yes. In fact, two of them.

First, we keep our repository running the most recent release so we
can eat our own dog food, yes, but that is a far cry from treating
that repository as a testbed. I don't want my (or anyone's else's)
work hindered because some well-intending developer is "testing"
locking on our live repository.

Secondly, since we're aren't going to be "testing" locking using our
repository (see above), it follows that the only type of locking in
use there will be real, I-gotta-lock-to-save-folks-from-wasting-time
locking. And I think that lock emails play a key role in preventing
people from wasting time.

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:47:56 2005

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