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

Re: subversion and locking

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-05-11 17:16:06 CEST

On May 11, 2005, at 8:53 AM, Simon Whittaker wrote:

> Hi All,
> I have recently installed subversion on a debian system and seem to
> have everything running quite happily for a multi-user environment.
> My problem now lies in the fact that my team are not happy working
> in a Copy-Modify-Merge environment as they do not feel it would
> work for them. They require the repository to block anyone else
> from checking out the file until it has been committed again.

Are all of the files binary formats? Ones that can't be merged? Or
they mostly source code? If the latter, then I suggest you might
have an education problem, rather than a requirements problem. I
suggest that you (and your team, especially) read the copy-modify-
merge discussion in chapter 2 of the book.

> This leaves me with a couple of options:
> 1/wait for version 1.2 to be released and _hope_ that it fulfills
> my expectations as regards locking.

Well, that's only a week away. You can test the rc3 candidate right
now if you want. There are also release notes describing the locking


The new locking feature certainly *can* be used to emulate VSS, but
it's really meant to be used only on unmergable binary files (where
lock-modify-unlock is truly required).

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 11 19:08:27 2005

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.