Re: Access configuration for leaves in one working copy

It should be one working copy to be able to move resources from one leaf
to another or to commit changes that affect multiple leaves in one
changeset. The leaves belong to one project, so it was a logical choice
to have them in one working copy.

Regards,
Holger

On 07.09.2015 16:20, Eric Johnson wrote:
> Why do you need one working copy?
>
>> On Sep 7, 2015, at 5:31 AM, Holger Schmidt <Holger.Schmidt_at_zmdi.com> wrote:
>>
>> Hi,
>>
>> There is a repository with this directory tree:
>>
>> root
>> +- dir_a
>> +- dir_b
>> | +- dir_c
>> | +- dir_d
>> +- dir_e
>> +- dir_f
>> +- dir_g
>>
>> Because there is sensible data in there user usr_u has read/write
>> access only to dir_c and dir_g.
>>
>> Question: How do I configure this with the path based authorization
>> (Apache + mod_authz_svn + AuthzSVNAccessFile) and with one working
>> copy?
Received on 2015-09-07 16:34:26 CEST