]> Launch a private p4d in a local directory If you are working with an offline repository in a local directory, vcp can launch a p4d in that directory on a random hi-numbered TCP port for you. p4 yes no Directory to run p4d in Enter the directory to launch the p4d in. VCP will test to see if this is a valid directory when you hit Enter. P4 Host name, including port Enter the name and port of the p4d to read from, separated by a colon. Leave empty to use the p4's default of the P4HOST environment variable if set or "perforce:1666" if not. P4 user id Enter the user_id (P4USER) value needed to access the server. Leave empty to use p4's default P4USER logic. ??? Password If a password (P4PASSWD) is needed to access the server, enter it here. WARNING: password will be echoed in plain text to the terminal. Files to copy If you want to copy a portion of the source repository, enter a p4 filespec starting with the depot name. Do not enter any revision or change number information. //... Follow 'branch into' flag Causes VCP to notice "branch into" messages in the output of p4's filelog command and. If the file that's the target of the p4 integrate (branch) command is revision number #1, adds the target to the list of exported files. This usually needs a --rev-root option to set the rev root to be high enough in the directory tree to include all branches (it's an error to export a file that is not under the rev root).