[p4] Limiting users ability to create new branches
rusty at rcjacksonconsulting.com
Wed Feb 27 10:34:22 PST 2008
No, the undoc help says that you can use the =branch right to prevent people
from branching files.
On 2/27/08, Jamison, Shawn <sjamison at ciena.com> wrote:
> Wouldn't that only work if they use a branch spec?
> Wouldn't I have to parse the files section of a change list and validate
> that the depot path is really a new branch?
> -Shawn Jamison>
> Ciena Corp.
> Perforce Admin
> -----Original Message-----
> From: Looney, James B (N-ULA) [mailto:james.b.looney at lmco.com]
> Sent: Wednesday, February 27, 2008 10:11 AM
> To: Jamison, Shawn; perforce-user at perforce.com
> Subject: RE: [p4] Limiting users ability to create new branches
> 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(
> > -----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
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user