Perforce 2007.2 Command Reference | ||
<< Previous Chapter p4 info |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 integrated |
The process is complete when you p4 submit toFile to the depot.
To specify multiple files, use wildcards in fromFile and toFile. Any wildcards used in fromFile must match identical wildcards in toFile. Perforce compares the fromFile pattern to the toFile pattern, creates a list of fromFile/toFile pairs, and performs an integration on each pair.
The syntax p4 integrate fromFiles toFiles requires you to specify the mapping between fromFiles and toFiles each time changes need to be propagated from fromFiles to toFiles. Alternatively, use p4 branch to store the mappings between fromFiles and toFiles in a branch view, and then use p4 integrate -b branchview whenever you need to propagate changes between fromFiles and toFiles.
-b branchname [toFiles...] |
Integrate the files using the sourceFile/targetFile mappings included in the branch view of branchname. If the toFiles argument is included, include only those target files in the branch view that match the pattern specified by toFiles. |
-n |
Display the integrations this command would perform without actually performing them. |
-v |
Open files for branching without copying toFiles into the client workspace. Without this flag, p4 integrate copies newly-branched toFiles into the client workspace from fromFiles. When the -v (virtual) flag is used, Perforce won't copy toFiles to the client workspace. Instead, you can fetch them with p4 sync when you need them. |
-c changelist# |
Open the toFiles for branch, integrate, or delete in the specified pending changelist. If this option is not provided, the files are opened in the default changelist. |
See the Global Options section. |
Perforce 2007.2 Command Reference | ||
<< Previous Chapter p4 info |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 integrated |