RE: Feature request

Hi there!
 
In Subversion effective use of locking works the other way around. By setting the property svn:needs-lock on a file it will become read-only for everyone, effectively creating the need to get the lock for that file *before* editing. (Which will fails if someone already has the lock.)
 
Please read the documentation:
http://tortoisesvn.sourceforge.net/docs/release/TortoiseSVN_en/ch05s18.html#tsvn-DUG-locking-how
 
I'm sure the user-list will be able to answer all your further questions!
 
(If you still thinks you need this feature please read the FAQ: http://tortoisesvn.sourceforge.net/node/163 )
 
Hans-Emil
 
PS. The property is still incorrectly spelled "svn:need-lock" in the FAQ-entry... DS.

________________________________

From: Humphrey Drummond [mailto:hum3@drummond.info]
Sent: Tue 2006-04-18 14:55
To: dev@tortoisesvn.tigris.org
Subject: Feature request

Hi Tortoisesvn

When a file is locked by user A and another user, B, does an update could that file be marked read only on user's B computer to indicate the lock (and when unlocked to be marked read write if read only).

This would make the locks more useful and might make the conflict more visible earlier in the editing cycle.

I like the product

Regards

Humphrey Drummond
Received on Tue Apr 18 15:53:22 2006