[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 06:39:31 CEST

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

If the file has svn:needs-lock set, then only the client will enforce
that you must lock the file before editing and committing it. But who
cares? You can't meaningfully distinguish between me locking,
committing, and unlocking the file in close succession and simply
committing 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 06:40:43 2005

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