[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 03:22:50 CEST

----- Original Message -----
From: "Richard P. Welty" <rwelty@suespammers.org>
To: <users@subversion.tigris.org>
Sent: Thursday, June 08, 2006 8:35 PM
Subject: Re: Subversion 101: To lock or not to lock..

> Andy Levy wrote:
>> No SCM system can cure a lack of communication. It can enable and
>> assist communication at the code level, but if the developers aren't
>> talking (which sounds like it may be the case), the project is already
>> in trouble - and fighting over lock vs. copy/merge in Subversion isn't
>> going to save it.
> day job has the misfortune of being a PVCS shop; nothing but locking.
> it can be remarkably irritating when the developer who has some key
> file locked is MIA and there's something critical to be done Right This
> Minute. the day job's version control is managed by another group
> on another floor, and it takes an act of god (or senior management)
> to get the locks broken.
> count this as one vote against locking,
> richard

Fortunately, lock breaking is now fairly easy with recent versions of

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 9 03:24:28 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.