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

Re: Line endings

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Sat, 21 May 2011 09:09:44 +0100

On 21 May 2011 07:32, John Emmas <johne53_at_tiscali.co.uk> wrote:
> On 20 May 2011, at 15:19, John Emmas wrote:
>
>>
>> 1) What does it mean when it says "Apply Property Recursively"?  I assumed that if I selected some folders along with my source files, the new eol-style would be propagated to the properties of any source files in those folders but that doesn't happen.
>>
> I figured out what the problem was.  When I include some folders in my selection, the first couple seem to work okay but it stops applying my selection from the third folder onwards.  If I open that folder and select a single file at random, when I try to change its eol-style property I get an error message telling me that my working copy is locked.  This applies to all the files in that particular folder - but not to any of the others.
>
> I'm pretty certain it shouldn't be locked.  None of the other files or folders are locked for this project.  How do I remove the locked status?

Unfortunately SVN's use of the word 'lock' is ambiguous and can refer
to working copy locks which you apply yourself to prevent others from
committing file(s) to the repository, or the OS file locking mechanism
which is used under the hood by SVN. In this case it's the latter. You
need to run SVN cleanup.

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2743221
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-05-21 10:09:52 CEST

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

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