That's actually only half the truth.
By setting svn:needs-lock, the files will be read only when you check
them out. If you acquire a lock, the file will be read enabled. However,
if a user decides to make the file writable by using chmod +w (or
unchecking the Read only tick in Windows), there is nothing that
prevents him from editing the file and then committing it.
The locking mechanism is just for communication between team members. If
you encounter a read-only file, the warning lights should flash, and you
should get a lock on it before doing anything. If a team member fails to
do that, and edit it anyway, he is undermining the system and may cause
trouble for his team.
I would suggest some kind of clever hook script similar to the one that
prevents tags from being edited.
Kjell H A
Steve Williams wrote:
> Andrew Bell wrote:
>> Is there a property or something that I can set so that a file can be
>> cheked in, once it, won't get committed unless you do something
>> special, even if you change it?
>
> Add the svn:needs-lock property to the file. Then a user needs to get
> a lock on the file before committing it.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 16 10:32:07 2005