Either Van or Tom mentioned that "something that should never be committed, was". Was it sql/mifosdbcreationscript.sql? Here's another encouraging word to use a Subversion lock on that file!
http://svnbook.red-bean.com/en/1.4/svn.advanced.locking.html SVN locks are not typically used to hold off commits for a particular node (node meaning file or directory), but rather to indicate that work is in progress. I would expect that the svn server configuration (apache conf or svnserve conf) would be the best place to limit write access to this file. However, the lock mechanism should work fine for now, especially if a descriptive comment is used, like: "This lock is in place to prevent commits for this file that should never be committed. No one is currently working on this file." Another possibility is setting the "svn:needs-lock" property on the file. This makes it so invoking a lock is necessary before committing the node. Either setting "svn:needs-lock" or just locking the file would have the effect of forcing the committer to do something extra before committing that file. I don't think setting the lock will increment the global revision number, but setting the "svn:needs-lock" property would result in a new revision. -- Adam Monsen ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
