[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Multiple access filess when using SVNParentPath

From: Carlos Alberto Costa Beppler <beppler_at_gmail.com>
Date: 2005-12-08 14:54:09 CET

This is exactly what I want.

Using SVNPath it works very well, except I must restart the server
every time I create a new repository.

On 12/8/05, Branko Čibej <brane@xbc.nu> wrote:
> Ben Collins-Sussman wrote:
> > Hm, that seems like pretty unusual use-case. Admins are the ones who
> > typically manage authz policy files, not arbitrary groups of users.
> >
> Yes. The devil lies in the definition of "admin" -- specifically,
> "server admin" vs. "repository admin".
> At work, I created a similar setup (without the SVNParentPath) -- the
> server admin can create repositories, but the repository admin can edit
> the mod_dav_svn authz.conf file, which is stored in the repository
> itself. That way, project managers can add or remove peoples' access to
> the project's repository without having to bug the IT department -- or,
> worse yet, me! :)
> -- Brane
Received on Thu Dec 8 14:56:18 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.