On Tue, Dec 21, 2010 at 9:46 AM, David Aldrich 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
On Tue, Dec 21, 2010 at 12:28:29PM -0500, David Weintraub wrote:
> On Tue, Dec 21, 2010 at 10:59 AM, David Aldrich
> wrote:
> > Thanks for your help. Yes, the branches, tags, and trunk directories are at
> > the root. In your suggestion, I am worried that a developer might create a
> > branch co
On Tue, Dec 21, 2010 at 10:59 AM, David Aldrich
wrote:
> Thanks for your help. Yes, the branches, tags, and trunk directories are at
> the root. In your suggestion, I am worried that a developer might create a
> branch containing ConfidentialFolder in /branches rather than in
> /branches/Confid
problem?
David
-Original Message-
From: David Weintraub [mailto:qazw...@gmail.com]
Sent: 21 December 2010 15:40
To: David Aldrich
Cc: users@subversion.apache.org
Subject: Re: An access permissions problem
It looks like the, branches, tags, and trunk directories are at the
root of your
It looks like the, branches, tags, and trunk directories are at the
root of your repository. What if you create the confidential branches
under their own folder under the branches and tags directories instead
of directly under those directories?
Then, you could specify it this way:
[myproj:/trunk
Hi
We host each of our projects in a separate svn repo and control access
permissions via Apache.
In one large project, we need to limit the visibility of a few confidential
files. We have done this by specifying something like:
[myproj:/trunk/ConfidentialFolder]
@myPrivilegedGroup = rw
* =
