svn:needs-lock not recognized if it has an empty value

[GoogleCodeExporter]

Reported on the mailing list:
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=30277
23

After upgrading from tsvn-1.6.15 to 1.7.10 the behavior for the lock icon 
overlay is different:

If the svn:needs-lock property is set but has no value then in 1.7.10 the 
normal (green) overlay icon is displayed instead of the readonly (grey) one.

The Subversion book says about svn:needs-lock
[1] 
http://svnbook.red-bean.com/en/1.7/svn.ref.properties.html#svn.ref.properties.ve
rsioned-props:
If present on a file, tells the client to make the file read-only in the 
working copy, as a reminder that the file should be locked before editing 
begins.
[2] 
http://svnbook.red-bean.com/en/1.7/svn.advanced.locking.html#svn.advanced.lockin
g.lock-communication: 
If that property is attached to a file (regardless of its value, which is 
irrelevant), Subversion will try to use filesystem-level permissions to make 
the file read-only—unless, of course, the user has explicitly locked the file.

It would save us a lot of explanations to our users if the readonly (grey) icon 
overlay is displayed again regardless the value of svn:needs-lock.

Original issue reported on code.google.com by tortoisesvn on 12 Nov 2012 at 9:03

[GoogleCodeExporter]

This issue was closed by revision r23440.

Original comment by tortoisesvn on 12 Nov 2012 at 9:06

• Changed state: Fixed

[GoogleCodeExporter]

This issue was closed by revision r23468.

Original comment by tortoisesvn on 13 Nov 2012 at 7:24