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

Re: svn commit: r14031 - trunk/subversion/clients/cmdline

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2005-04-10 19:22:06 CEST

On Sun, 2005-04-10 at 13:16, Scott Palmer wrote:
> > Uh, if I have a lock on a file, it will be enforced by the server in
> > that you can't modify it. (Without breaking or stealing the lock,
> > which I think can be restricted by hook scripts if nothing else.)

> That's not what was stated earlier in this thread:
> "Not true. svn:needs-lock is a client-side thing. It communicates to
> your fellow collegues that this file must be locked. The repository
> doesn't care."

svn:needs-lock doesn't mean "someone has a lock on this file". It is
set manually, and it means "the client should try to force you to lock
this file before editing it".

> "The repository doesn't care" - you can commit changes without having
> the file locked.

Correct, in the sense that svn:needs-lock will not cause the server to
enforce that you have the file locked in order to commit to it. But
someone else having the file locked will cause the server to enforce
that you have to break or steal the lock in order to commit to it.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 10 19:26:05 2005

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