Perforce 2006.1 Command Reference | ||
<< Previous Chapter p4 annotate |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 branches |
Once you have named and created a branch specification, integrate files by typing p4 integrate -b branchname; the branch specification automatically maps all toFiles to their corresponding fromFiles.
Saving a p4 branch form has no immediate effect on any files in the depot or your client workspace; you must call p4 integrate -b branchspecname to create the branched files in your workspace and to open the files in a changelist.
-d |
Delete the named branch specification. Files are not affected by this operation; only the stored mapping from one codeline to another is deleted. Normally, only the user who created the branch can use this flag. |
-f |
Force flag. Combined with -d, allows Perforce administrators to delete branches they don't own. Also allows administrators to change the modification date of the branch specification (the Update: field is writable when using the -f flag). |
-i |
Read the branch specification from standard input without invoking an editor. |
-o |
Write the branch specification to standard output without invoking an editor. |
g-opts |
See the Global Options section. |
Perforce 2006.1 Command Reference | ||
<< Previous Chapter p4 annotate |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 branches |