You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Rama Mohan Rao Peruri <ra...@dbs.com> on 2006/08/01 03:29:31 UTC

Propogating Changes to SVN Authorisation Policy

Hi,

 

I am using SVN 1.3.0 and Tortoise SVN 1.3.4.6692.  SVN is configured for
access via Apache Http server using https.  

 

I have recently modified the authorization policy 

Re: Propogating Changes to SVN Authorisation Policy

Posted by Andy Levy <an...@gmail.com>.
On 7/31/06, Rama Mohan Rao Peruri <ra...@dbs.com> wrote:
> I am using SVN 1.3.0 and Tortoise SVN 1.3.4.6692.  SVN is configured for
> access via Apache Http server using https.
>
> I have recently modified the authorization policy
>
> From :  All users have access to Directory1/ Directory2
>
> To:       User1 and User2 have no access to Directory1 / Directory2.
>
> I noticed that SVN Update did not delete Directory2 from the local copy of
> user1 and user2.
>
> Is there a way in which I can configure TortoiseSVN to ensure that all
> directories for which I do not have access in SVN are deleted automatically?

Subversion shouldn't delete anything from a WC unless it was deleted
in the repository as well.  Your users are already locked out from
checking in updates to these directories, so unless your concern is
that they might see something that they used to be allowed to but no
longer do, there's no harm in the files remaining.  And they won't see
any future changes to those files.

Even if it did do this, what assurance do you have that the user
didn't copy the files/directories outside the WC before you
implemented this policy change?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org