On Tue, Dec 21, 2010 at 9:46 AM, David Aldrich <david.aldr...@eu.nec.com> wrote: > Hi > > > > We host each of our projects in a separate svn repo and control access > permissions via Apache.
Put the confidential materials in a separate repository. Use svn:externals to access that separate, more securely managed repository inside of working copies. This eliminates the ability to "svn copy" the material inside the unsecured repository, but that sounds acceptable. It makes managing them on the client end a bit trickier, but it is much more stable on the server side than trying to repeatedly pick and choose the configuration of your Apache, authz, pre-commit, or other tools.
