[p4] Efficiency of protect

[Stephen Vance]

Sushree --

In your branching example, if the newyork_users branch 
//depot/main/dev/... to //depot/main/jam/dev/... the bangalore_users can 
only operate on the copy under //depot/main/jam/dev/.... If your purpose 
is to completely hide the contents of that source, you have an issue to 
overcome. If you just want to protect the copy under 
//depot/main/dev/... then you don't have a problem.

You may also want to look at the "branch" protection level. You can find 
it as an undocumented feature under 'p4 help undoc'.

Steve

Sushree Tripathy wrote:
> Hi All,
>
> I have two groups say
>
> bangalore_users
> newyork_users
>
> I have the following protections:
> read group bangalore_users * //depot/main/...
> write group bangalore_users * //depot/main/jam/...
> read group bangalore_users * -//depot/main/dev/...
> wirte group newyork_users * //depot/main/...
>
> But what if someone from newyork_users group branches
> the files under //depot/main/dev/... to
> //depot/main/jam/dev/...
>
> Then bangalore_users get write access to files under
> //depot/main/dev/... which they should not have
> access.
>
> I do understand that the above example can be stated
> as a mischief but my point is that are the protections
> that efficient w.r.t files/folders?
>
> Also can we implement some triggers so that we
> restrict branching paths by which files become visible
> to restricted users?
>
> Please suggest....
>
>
> Regards,
> Sushree.
>
>
>
>  
> ____________________________________________________________________________________
> Now that's room service!  Choose from over 150,000 hotels
> in 45,000 destinations on Yahoo! Travel to find your fit.
> http://farechase.yahoo.com/promo-generic-14795097
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>