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

Re: issue for svn:needs-lock

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Tue, 29 Apr 2008 20:46:18 +0200

syoung_at_rockwellcollins.com wrote:
> Hi,
> I have a problem in using this svn:needs-lock property to make files
> read-only. Hope to get some answers from experts in this group.
> First, I added this svn:needs-lock property to a file with a value of
> one through Context Menu ->TortoiseSVN -> Properties
> Second, I refreshed the Windows Explorer to get the status updated for
> this file.
> Now, the problem is that the icon overlay in Windows Explorer shows the
> status of this file as modified, not read-only. Since the status of file
> is shown as modified (icon overlay shown as exclamation), I can edit
> this file without warning shown up, even though this svn:needs-lock
> property is set for this file.
> According to the TortoiseSVN manual, once the svn:needs-lock property is
> set for a file, this file becomes a read-only file and the icon overlay
> is still a check mark.
> Can anyone tell me whether I missed anything???
> I am using TortoiseSVN 1.4.8.

Since you just added the property, the file is modified (the properties
are new, so you the status is 'modified' to indicate that you need to
commit those changes first).
So: commit that property change, and after the commit (or after the next
update, I'm not quite sure) the file will be made read-only.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net

Received on 2008-04-29 20:46:41 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.