Guten Tag David Myers, am Samstag, 16. Juli 2011 um 22:14 schrieben Sie: > Please help me clarify this so as I can propose the use of a subversion > to my colleagues, and give eloquent and correct answers to any of their > queries.
First of all, nothing is committed automatically by default and therefore can not be committed by accident. Even in your described scenario of accidently changing a file which shouldn't have changed, it doesn't get committed automatically. One has to commit the file as a separate process. It may be possible that the changed file gets committed by accident with other changes which should get committed, but this depends on your repository layout and therefore can be prevented by proper layout. So, do you really need the administrative overhead of making the file read only? If you really want it read only, I would just use path based authorization with a group which consists of all users which normally modify the files in question, therefore have granted write permissions and after they agree that nor further modification is needed, change write to read permissions. http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.serverconfig.pathbasedauthz Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig Telefon: Potsdam: 0331-743881-0 E-Mail: tschoen...@am-soft.de Web: http://www.am-soft.de AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow
