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

Re: Operational restrictions in svn?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-11-05 21:01:36 CET

On Nov 4, 2004, at 8:18 PM, Steve Cramer wrote:

> The issue is really just that our management want some assurances that
> no developer can, either maliciously or accidentally, create branches
> or perform wide-ranging merges within the repository.

In Subversion, "creating a branch" is just creating a new directory in
the repository, one which is a copy of another. So if you prevent
users from doing that (using read/write perms on repository paths),
then you've prevented branch creation.

In Subversion, a "merge" is a two part operation. A user asks their
client to compare two server-trees, and then apply the difference as
local edits to a working-copy. Then the user commits the working-copy
changes. Once again, you can prevent this from happening by
restricting read access to certain trees, or by restricting write
access to certain places.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 5 21:03:15 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.