[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: Brian W. Fitzpatrick <fitz_at_red-bean.com>
Date: 2005-04-09 04:28:22 CEST

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


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 9 04:30:23 2005

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