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

RE: Atomicity of locks and needs-lock

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2006-04-29 23:37:44 CEST

On Sat, 2006-04-29 at 17:32 -0400, Edward Harvey wrote:
> If someone locked the file, they must be thinking that your changes,
> whatever they are, won't be mergeable.

They are thinking *they* do not want to merge any changes you might
make. You might know better (because you know what change you're going
to make), or you might be in a better position to do such a merge.

> No user has reason to lock a file, unless they believe that you
> shouldn't work on it right now.

No, unless they believe you shouldn't *change* it right now.

You lock a file to protect yourself. You set svn:needs-lock on a file
to protect others.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 29 23:38:47 2006

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

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