If you are committing any version of the config file to the repository, then maybe you should think about branching -- you could have dev, staging, and production branches of the file -- then nothing you did to your dev config would have anything to do with your production config. But if you needed to, svn would be able to merge changes between the different versions since they all came from the same original file.
I think your use of locking is a common practice, but I don't know. I think it's usually used to prevent conflicts in binary files. Hopefully someone else will clarify that... -Ray --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/versions?hl=en -~----------~----~----~----~------~----~------~--~---
