+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
$Id: //guest/peter_jackson/About.TXT#1 $
$Change: 26141 $ $DateTime: 2019/10/24 08:25:55 $ $Author: peter_jackson $
-----------------------------------------------------------------------
# About the Perforce repository and its use by PNJ
Confidentiality: public
Keywords: None
Readership: PNJ
This is the root directory of my personal material in the Perforce
guest depot. Adjacent to this directory in my standard workspace
mappings are other guest directory trees of inetrest, including those
from "perforce_software" itself.
The Perforce repository itself has three visible depots:
//guest
Containing user and Perforce-contributed material;
//public
Containing JAM and an almost empty Perforce directory tree;
//spec
the spec depot.
Anything I actually modify is to be branched into the PNJ tree
and merged back in conjunction with the owner of the originating
branch.
I can't find a document suggesting a preferred convention for workspace
names. I'm using:
<username>-<hostname>-<projectname>
Files in this directory are:
About.TXT This file
pcp.html Redirect to PCP info
The pcp document was part of a Perforce Consulting Partner infrastructure
that I suspect is no longer operational.
Updates
=======
1. PNJ 2019-10-24 Started
-- End of note