[p4] Coordinating Branches
Eramo, Mark
meramo at 170Systems.com
Fri Apr 6 06:30:36 PDT 2007
You should probably be able to do this with a trigger.
For example, Say the source files your interested in is the exact same
in b1 and b2. If that's the case then you have to files that are the
same in b1 and b2, read only in b2. This way, users cannot update those.
The files in b1 are read/write.
You setup a trigger on the files in b1 so that when one is updated that
change is propagated to the same file in b2.
Now there might be some files in b2 that do not exist in b1. Those can
be read/write in b2.
There is documentation on the Perforce website on triggers:
http://www.perforce.com/perforce/technotes/note028.html
Also, I think you will find information in the Perforce System
Administration guide and the "Practical Perforce" book that is available
from various online retailers.
Regards,
Mark
-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of R K
Sent: Thursday, April 05, 2007 11:52 PM
To: perforce-user at perforce.com
Subject: [p4] Coordinating Branches
All,
Suppose there are 2 branches say B1 and B2 . If I make changes to a file
and
submit , is there a way in perforce to submit it in B2 also ( B1 is a
subset of B2) . If there is a way how can it be done ?
Regards
Ram
_______________________________________________
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