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

Re: Subversion 101: To lock or not to lock..

From: Nico Kadel-Garcia <nkadel_at_comcast.net>
Date: 2006-06-09 14:07:39 CEST

Richard P. Welty wrote:
> Nico Kadel-Garcia wrote:
>> Fortunately, lock breaking is now fairly easy with recent versions of
>> Subversion.
> which is appreciated, certainly, but locks under the wrong kind of
> tight fisted management
> can be hard to break regardless of how nicely the software handles it.
> richard

Subversion locks can be broken by anyone with write access to the particular
project. The only way to "tightfist" that is to do it socially, or somehow
write in some procedure that only allows certain people to do it.

Are you referring to the social issue, or the software issue?

Now, one big problem of locks is that as the programmer without the lock
makes changes and test setups, they can't enter them in source control. That
becomes a complete violation of source control, and can lead to lost work.
(But you know that!)

This is why subversion has branches, and the ability to merge among them:
why aren't your authors using them?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 9 14:08:46 2006

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

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