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

RE: Atomicity of locks and needs-lock

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2006-04-30 01:09:32 CEST

It's clear to me that you have a particular mental model of what it
means to lock a file, that it does not match the model the developers
had when we designed the locking system, and that you're very convinced
that yours is right and ours is wrong. I'm going to drop out of this
conversation, as I doubt it will go anywhere under those circumstances.
One last clarification:

On Sat, 2006-04-29 at 19:06 -0400, Edward Harvey wrote:
> > > No user has reason to lock a file, unless they believe that you
> > > shouldn't work on it right now.
> >
> > No, unless they believe you shouldn't *change* it right now.
>
> What's the difference? Work on a file = Change a file, as far as I'm
> concerned. Perhaps the comment was meant to simply be argumentative.

It would have been clearer for me to say, "they believe you shouldn't
*change* it in the repository right now."

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 30 01:10:40 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.