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

Re: Locking: RFC: svn:needs-lock behaviors

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-02-02 23:00:37 CET

"Brian W. Fitzpatrick" <fitz@collab.net> wrote on 02/02/2005 04:53:37 PM:

[snip]
 
> Propset:
> - Setting the svn:needs-lock property sets the file to read-only
> (It also canonicalizes the value to '*')

Before setting the file to read-only, shouldn't it check to see if it is
locally modified?

You do not mention unlock. But I would assume if you run a command that
unlocks a file with this property set, whether it be the unlock or commit
command, that it would set the file to read-only?

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 2 23:01:49 2005

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