setup
-----
set P4PORT=perforce:1666
set P4PASSWORD=<password>		(only if passwords are setup)
set P4CLIENT=<clientname>	(workspace (one per machine), default to machine name)
				(A different m/c needs a different workspace)
set P4USER=<username>		(else defaults to username)
(ALTERNATE:
set P4CONFIG=p4config.txt	
(in a login script, where p4config.txt is a file holding the above information
in the format:
P4PORT=perforce:1666
P4PASSWORD=<password>
P4CLIENT=<clientname>)
- then on another (i.e.UNIX) machine:
setenv P4CLIENT <scriptname> (i.e. rivendell-script)
p4 client (probably need to change the text file, as below).
That's it. Then move to the dir, and add & submit the file to be perforced 

useful commands
--------------
p4 info			- gives information
p4 set			- gives information, with where set (useful if p4config.txt is used)
p4 client 		- sets file mapping
[this opens text file containing (example):
:::::::::::::::::::::::::::::::::::::::::::::::
client root 	d:\perforce
	//users/markje		//oric/users
        |_____________|	       |____________|
	      |		             |
            service		    client name
        (server location)
:::::::::::::::::::::::::::::::::::::::::::::::

Note:  	//oric is replaced by the root
	 /users could be 'markstuff' or 'perforce'
On Mac:
root: Mac Volume:Documents
//kevin-g3mac-4.1
- before directory list items indictates exclusion
]


p4 add <filename> 	- add file to p4 server
p4 edit			- notifies p4 that checks are being made
p4 sync			- brings files from server to workspace
p4 submit		- makes files (gives up after two attempts)
[this opens text file containing (example):
description -*Needs to be changed*
]
p4 have			- on client
p4 have ...		- at current directory and below (recursive)
p4 have *		- at current directory only (non recursive)
p4 diff <local file>    - difference between local file and file on server

Verbs can become adjectives, add -ed

p4 resolve		- for resolving
p4 lock			- for binary

To move files on perforce:
p4 integrate /users/markje/... //users/markje/stress/141/...
To mark as deleted and hide files:
p4 delete "users/markje/*"
To see changes that are pending (need submitting)
p4 changes -s pending
To see which files are opened
p4 opened -a | fidstr > junk

Remember
--------

Say what we're going to do		add	edit	delete	integrate	diff
Do it.							(notepad)
Say what we've done				submit

Can revert after add,edit, x, and delete, but must be before submit.
No need to submit a revert.


PERFORCE Bare Bones
-------------------

p4 edit -> edit in notepad
p4 diff - see change
p4 submit - return doc to server
p4 sync - go back to previous version
p4 client

//uk-src/PerforceLocal
p4 files - checked in on server
p4 have - checked out on client m/c
p4 help help - shows commands