[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: Scott Palmer <scott.palmer_at_2connected.org>
Date: 2005-04-10 19:16:03 CEST

On Apr 10, 2005, at 12:39 AM, Greg Hudson wrote:

> On Sat, 2005-04-09 at 20:44, Scott Palmer wrote:
>> Crap.. I wish I knew that before so I could whine about it. I now
>> consider locking to be 100% broken by design. What good is locking if
>> it isn't enforced?
> 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."

"The repository doesn't care" - you can commit changes without having
the file locked.
It appears that by not having the file locked changes are merely
*discouraged* by the client in that it will make the file read-only by


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:17:25 2005

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