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

> >> 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.

Lengthy discussion over at tsvn-devel, including dumb postings by me
suggesting the use of ACLs and that svn-libs implement a interface to
support "a daemon that would hook into the filesystem API and display
'please lock file first' messages."

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 10 03:11:57 2005