[p4] protect and where
karish at well.com
Sat Oct 27 09:46:34 PDT 2001
This isn't documented in either doc set (p4 help, Command Reference).
File a bug against the docs and fix your scripts; a user could break them
by changing a client spec.
At 12:25 PM 10/26/2001 -0700, Mike Castle wrote:
>Are settings in p4 protect supposed to affect the output of p4 where?
>I wanted to set it up so that a particular file is changed only in one
>branch (I'd worry about perms for migration in a bit).
>So I set up a protection like:
> write user * * -//testarea/.../foo.c
> read user * * //testarea/.../foo.c
> write group systems * //testarea/main/foo.c
>However, now p4 where shows:
>//testarea/... //wraptor2/testarea/... /home/mcastle/src/testarea/...
>//testarea/.../foo.c //wraptor2/testarea/.../foo.c /home/mcastle/src/testarea/.../foo.c
>//testarea/main/foo.c //wraptor2/testarea/main/foo.c /home/mcastle/src/testarea/main/foo.c
>Which was completely unexpected (and broke some of my build scripts :-)
>Actually, since I'm going to have to handle integrations, I'll probably
>make this a trigger anyway.
>But still, that was not what I expected.
>Did I not read something that would have prepared me for that output?
Chuck Karish karish at well.com (415) 317-0182
More information about the perforce-user