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

Re: difference between TSVN and SVN on a server

From: Ron Wilson <ronw.mrmx_at_gmail.com>
Date: 2007-09-20 18:48:15 CEST

You could setup one repository per project, make each repository only
accessable to project members. If a project contains any documents
that non-member need to access, you can set up a post commit hook to
automatically export those documents to a parallel document tree. (The
project members would, of course, need write access to the
corresponding folders in the parallel tree.)

Of course, if you setup a proper SVN server, you will get more control
over access without needing a parallel tree.

On 9/20/07, savera singh <saverasingh@yahoo.com> wrote:
[...]
> Regards control -- we do
> need to restrict access to non-project team members.
> Please suggest.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Sep 20 18:48:31 2007

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

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