Perforce 2006.1 Command Reference
<< Previous Chapter
p4 integrate
Table of Contents
Index
Perforce on the Web
Next Chapter >>
p4 job

p4 integrated

Synopsis

Show integrations that have been submitted.

Syntax

p4 [g-opts] integrated [ -r ] [ -b branch ] file...

Description

The p4 integrated command shows the integration history of the selected files, in the format:

where

If a file toFile was ever integrated from a file fromFile, and both toFile and fromFile match the p4 integrated filepattern argument, each integrated action is listed twice in the p4 integrated output: once in its from form, and once in its into form, as described above.

If the optional -b branch flag is used, only files integrated from the source to target files in the branch view are shown.

If the optional -r flag is provided, the mappings in the branch view are reversed. This flag requires the use of the -b branch flag.

Options

g-opts

See the Global Options section.

Usage Notes

Can File Arguments Use
Revision Specifier?

Can File Arguments Use
Revision Range?

Minimal Access Level Required

No

No

list

Related Commands

To see a list of integrations that have not yet been resolved

p4 resolve -n

To view a list of integrations that have been resolved but not yet submitted

p4 resolved

To perform an integration

p4 integrate

To view the actions taken for all revisions of a particular file (including all the files from which that particular file was integrated)

p4 filelog [-i] file


Perforce 2006.1 Command Reference
<< Previous Chapter
p4 integrate
Table of Contents
Index
Perforce on the Web
Next Chapter >>
p4 job
Please send comments and questions about this manual to [email protected].
Copyright 1999-2006 Perforce Software. All rights reserved.
Last updated: 06/23/06