[p4] permissions problem

Paul Goffin Paul.Goffin at aepsystems.com
Fri Mar 4 02:09:06 PST 2005

Yes.  try "p4 help undoc" and you will see this information about
additional protection levels:
    Protections =read, =branch, =open, =write
        In addition to the normal protection levels (list, read, write,
        open, super, and review) there are four protection rights
        available in the 'p4 protect' table.  Unlike the levels, these
        '=rights' only include the specific right and not all the lesser
        rights.  This makes it possible to deny individual rights
        having to then re-grant lesser rights.
        Additionally, there is a new right =branch (normally included
        by level 'read' and above) that permits the files to be used as
        the source for 'p4 integrate'.  You can prevent files from being
        branched by denying the =branch right.
-----Original Message-----
From: Micheal.OShea at swisscom.com [mailto:Micheal.OShea at swisscom.com]
Sent: 04 March 2005 08:52
To: perforce-user at perforce.com
Subject: [p4] permissions problem

Hi folks, 
We have a perforce depot laid out like, 


Easy enough except we have some folks who cannot see the point of this
and insist on adding files straight in to //depot/live/...

Is there any way we can only allow them to add to //depot/live/... via
branching and disallow them from adding files directly?

Many thanks in advance, 

This email and any files transmitted with it are confidential 
and intended solely for the use of the individual or entity to
whom they are addressed. If you have received this email
in error please notify the postmaster at the address below.
ITS-Support at aepsystems.com

Unless the contrary is specifically indicated above nothing in
this message is intended to constitute an electronic signature
within the meaning of the Electronic Commerce Act 2000 or
similar legislation enacted elsewhere in the world.

This footnote also confirms that this email message has been swept for the presence of computer viruses.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.perforce.com/pipermail/perforce-user/attachments/20050304/0eab2fec/attachment-0007.html>

More information about the perforce-user mailing list