Perforce 2003.1 Command Reference

p4 branchp4 branchSynopsisCreate or edit a branch view specification.Syntaxp4 [g-opts] branch [ -f ] branchspecp4 [g-opts] branch -o branchspecp4 [g-opts] branch -d [ -f ] branchspecp4 [g-opts] branch -i [ -f ]Descriptionp4 branch allows you to store a mapping between two sets of files for use with p4integrate. This command displays a form: enter a view that expresses the mappingsbetween the files you’re integrating from (the fromFiles) and the files you’re integratingto (the toFiles), specifying both sides of the view in depot syntax.Once the branch specification has been created and named, you can integrate files bytyping p4 integrate -b branchspecname; the branch specification automatically mapsall toFiles to their corresponding fromFiles.Completing p4 branch has no immediate effect on any files in the depot. Perforce doesn’tcreate the branched files in the client workspace until you first call p4 integrate -bbranchspecname.Form FieldsField Name Type DescriptionBranch: read-only The branch name, as provided on the command line.Owner: mandatory The owner of the branch specification. By default, thiswill be set to the user who created the branch. This fieldis unimportant unless the Option: field value islocked.Access: read-only The date the branch specification was last accessed.Update: read-only The date the branch specification was last changed.Perforce 2003.1 Command Reference 15