RE: Atomicity of locks and needs-lock

Edward Harvey wrote:

> If someone locked the file, they must be thinking that your changes,
> whatever they are, won't be mergeable.
>
Rubbish.

Say you are generating a release. You want to stop anyone else making
checkins for a day or so while you are doing that, so locking all the files
would seem a sensible move.

That doesn't stop anyone from making edits to some of the files in the
expectation that you will unlock them again and then they can merge them.
All it means is that you need some part of the repository to remain stable
for a period while you run test suites, update documentation etc.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 30 11:45:38 2006