Neels J Hofmeyr wrote on Wed, Aug 24, 2011 at 23:14:34 +0200: > On 08/24/2011 05:10 PM, Mark Phippard wrote: > > BTW, admins can also lock files in the repository to prevent accidental > > commits of sensitive information. > > That's a good point, actually. > > If I want to add an intentional change, I steal the lock. Then lock it back > (using a separate WC to lock the file for myself). The commit bails even > before the modifications are sent over the wire. It's a central config. >
Another option: use a pre-commit hook instead of locks. It does mean the local changes will be sent to the server --- which may be a problem. But then, you have the same problem with people (or admins) stealing the locks... > But: Say a template path is locked; the result is that everyone with a > filled-in template now gets failing commits all the time. Now you need a > convenience thing that excludes this locked file from commit locally. > > This still requires specific action on every single checkout to block the > exact right files. Users will be forced to do that, they can't run a plain > 'svn commit' and succeed. > > This would cover all the needs *except* that a new checkout should > local-hold automatically without further user action. > > (So we can add a prop for that, ok, and then we can use that prop and don't > need to duplicate with a changelists based implementation) > > ~Neels >
