[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: John Szakmeister <john_at_szakmeister.net>
Date: 2005-04-09 12:29:13 CEST

On Friday 08 April 2005 22:28, Brian W. Fitzpatrick wrote:
> On Apr 8, 2005, at 5:05 PM, Philip Martin wrote:
> > "Peter N. Lundblad" <peter@famlundblad.se> writes:
> >> 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.
> >
> > So a different client might bypass it? I didn't realise that (I'm
> > not all that interested in locking).
> svn:needs-lock is a communication mechanism for advisory
> purposes--nothing more. If svn:needs-lock is set on a property, it
> will be checked out read-only unless you have a lock on the file in
> question. Sure you can circumvent this on the OS level, but the point
> is that if a file comes into your wc read-only, it's a message to you
> that you should darned well lock the file before editing (for whatever
> reason--typically that it's a non-mergeable file).

The server will allow anyone to commit it without holding the lock token?
I at least thought there was another step there. Mainly, that if someone
other than the original holder of the lock wanted to commit, that they
would have to break the lock first. I'm off to read the locking notes...


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 9 13:24:47 2005

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