Re: subversion and locking
Ben Collins-Sussman wrote:
> 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.
The files are coldfusion code so should be able to be merged with no
probs but the problem lies with the userbase.
>> 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 UI:
> 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).
There was very strong dissent towards the idea of multiple users editing
the same file and I have been informed that any source control software
would _have_ to conform to the lock-modify-unlock system. If subversion
1.2 can emulate VSS in this capacity then I will use this otherwise I
will be using VSS :(
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed May 11 19:52:19 2005
This is an archived mail posted to the Subversion Users