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

Re: Repository permissions

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-08-28 18:08:14 CEST

On Fri, 2004-08-27 at 20:07, kfogel@collab.net wrote:
> Mike Ladwig <mladwig@comcast.net> writes:
> > 1. Use svnadmin dump and svndumpfilter to create a separate repository for
> > staff A that has no branch B. The disadvantage is that if the decision is
> > changed in the future, it will be hard to "remerge" the projects.
> >
> > 2. Setup for http access and use the http access controls (I found an email
> > suggesting that I can limit branch access using webdav). The (huge)
> > disadvantage here is that I will need to setup this new access method and
> > retrain all the developers to use it.
> (2) is not so hard, and will do what you want. Note that it's not
> just webdav, you may want to use mod_authz_svn.
> I don't see any other options besides the ones you mention.

And what retraining is necessary? The svn client uses URLs. You're
talking about switching from svn+ssh:// to http:// URLs. The user does
a new checkout, and then everything is the same.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Aug 28 18:09:28 2004

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

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