[p4] Limiting users ability to create new branches

Looney, James B (N-ULA) james.b.looney at lmco.com
Wed Feb 27 07:11:18 PST 2008


Sounds like you might want to use a form-in trigger on branches.  If you
see the name of a person in the development group, reject it.  See
Perforce's public depot ( http://public.perforce.com/public/index.html
)or the admin docs for more on triggers(
http://www.perforce.com/perforce/doc.042/manuals/p4sag/06_scripting.html
). 

-James

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of 
> Jamison, Shawn
> Sent: Wednesday, February 27, 2008 7:22 AM
> To: perforce-user at perforce.com
> Subject: [p4] Limiting users ability to create new branches
> 
> I have the express need to limit a development groups ability 
> to create
> new branches.
> 
> They seem to think that a new branch is the solution to every
> development problem.  
> 
> 
> Has anyone experienced this before or have any suggestions on how to
> accomplish this?  
> 	Besides sending a dude named Tony to visit them with at baseball
> bat...
> 
> Thanks
> -Shawn Jamison>
> Ciena Corp.
> Perforce Admin
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> 



More information about the perforce-user mailing list