Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have experienced strange functionality of subversion.
We are using latest 1.6 Svn server visual svn and tortoise svn 1.6.6
We have defined property svn:needs-lock to a file, then if you copy over file from different location it shows local change if you try to commit SVN it allows you to Commit even if you didn’t obtain the LOCK.
This is a big problem for us, please let us know how to force SVN not to allow commits without obtaining the lock.
Thanks.
The lock mechanism in Subversion will not give you, out of the box, a way to prevent commits without a lock first.
You might, emphasis on might, be able to handle that with server hooks, but I’m unsure. Perhaps you should ask a new question where you ask how to create a subversion server hook script that prevents people from committing changes if they don’t own the lock on the file first.
The lock mechanism is just a extra tool to manage problematic files, like designer files where the content gets moved around a lot (so merging is a pain), or for binary files, if you store those. But the lock mechanism is not, out of the box, there to prevent you from committing without a lock, it’s just a convenience, but can easily be circumvented.