On Jan 19, 2011, at 03:32, Jan Keirse wrote: > I'm not asking for a lock on part of the file, in fact if you think about > it I'm not asking a real lock, i'm only asking a notification, informing > the developer who else is working on the file.
[snip] > I'm not asking to automatically stop the user from > changing anything, I just would like them to be notified someone else is > working on the file so that they can talk to the other people to make sure > they are only working on logic and not design. Note that Subversion does have pre-lock and post-lock hooks that you can write scripts for. Note also that Subversion locks can, by default, be stolen by anyone. Combining these facts, you could write a post-lock hook that informs your team that someone has locked this file. (This information could be sent by any convenient means -- for example, by sending an email to a mailing list to which all team members are subscribed.) Anyone who feels they still need to work on the file after it has been locked by someone can steal the lock for themselves.
