[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:11:25 CEST

On Apr 9, 2005, at 9:10 PM, Molle Bestefich wrote:

>>>> Ha! Well that explains why I thought it was mandatory rather than
>>>> advisory. I was wondering where I got that idea :)
>>> Whoops, that paragraph is out of date, sorry. Somewhere along the
>>> line we decided not to have the server enforce that behavior.
>> 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? This seems as logical as making the client decide
>> who has write access to a repository.
> It's enforced by setting the DOS read-only bit, on Windows at least.

No, that just tries to prevent the editing of unlocked files on the
client side. It is unrelated to allowing those changes to be

A pre-commit hook works around it I guess, but without it locking is
something much different than what I was thinking it would be, and not
at all like what other revision control systems consider locking to be.


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:12:37 2005

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