Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We are using SubVersion to manage a big project, every one normally has to lock a file before to modify it, but on some new machine with Window 7 and SVN 64 bit also with this directive in the config file:

 ** = svn:needs-lock=true
 *.* = svn:needs-lock=true*

If a user with one of this new machine create a new file, this file will remain editable in every moment also without lock and without locking it and than causing a conflict.

How can I solve it?

share|improve this question
add comment

1 Answer 1

Eek. Merge, don't lock; this ain't CVS.

Likely the config file isn't actually being applied for whatever reason - where is this file located? You'll also need to make sure that enable-auto-props is set somewhere in the config.

To ensure that all your files have that property set regardless of client misconfiguration, add a pre-commit hook that rejects the commit if it's not present.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.