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

Re: Read-only files marked as svn:needs-lock?

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2007-07-27 18:54:43 CEST

Simon Large wrote:
> Hi folks,
> In our docs for 1.5 we say that read-only files are marked with the
> grey overlay. Does svn 1.5 give us a better way of detecting
> svn:needs-lock which means we no longer do this? I just tried making a
> file read-only and the overlay stays the same.

That depends :)
No seriously: SVN 1.3.x has an older working copy format, which does not
store the svn:needs-lock property in its entries file. And in those
working copies, svn_client_status() doesn't return the information
whether the svn:needs-lock property is set or not. That's why we show
the overlay for readonly files too.
Problem is: the entries file is only updated if during an 'svn update',
at least one file in a specific folder is updated. And AFAIK, the
svn:needs-lock property isn't cached in the entries file until that
specific file gets updated. So it is possible even with working copies
which have the new format (upgraded from 1.3.x) to *not* have the
property cached.

Of course, we could just document that and then tell people that they
may have to do a fresh checkout for the overlays to appear correctly.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Jul 27 18:53:27 2007

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

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