On 25/10/14 19:52, Mohsin wrote: > Please check this and let me know this should work for said requirement ? > > [Repo:/] > user1 = rw > user2 = rw > user3 = rw > > [trunk:/trunk/folder1/folder21] > user2 = > > [trunk:/trunk/folder1/folder2/folder31] > user3 =
While the above would work for the trunk paths the user required this to be enforced across copies (branches, tags) as well, at which point he was directed to adjust his repository layout to support that or to make the repository admins do their work. Selective restrictions on paths that are sub-trees of the normal level of working copies do not normally play well when using branching and merging, especially when setting something to no access as a user would have an incomplete view of the source tree. Path based authorization does, however, work very well and is intended to being applied to projects, branches and sub-modules. Andreas
