p4 interchanges

Synopsis

Report changes not yet integrated.

Syntax


p4 [g-opts] interchanges [-f -l -r -t -F] [-u user] fromFile[revRange] toFile
p4 [g-opts] interchanges [-f -l -r -t -F] [-u user] -b branchname [toFile[revRange] …]
p4 [g-opts] interchanges [-f -l -r -t -F] [-u user] -b branchname -s fromFile[revRange]
                         [toFile …]
p4 [g-opts] interchanges [-f -l -r -t -F] [-u user] -S stream [-P parent] [file[revRange]]
                         [toFile …]

Description

The p4 interchanges command lists changes that have not been integrated from a set of source files to a set of target files. The command also reports changes that consist solely of ignored integrations if those changes have not yet been integrated into the target.

Options

-b branchname

Use the source and target as defined by the specified branch specification.

-b branchname -s fromFile[RevRange] [toFiles …]

Preview bidirectional integrations (used by Perforce applications; see p4 integrate for details.)

-f

List files that require integration. For partially integrated changelists, files might be listed even if they were integrated individually.

-F

Used with -S, ignores a stream's expected flow. It can also force it to generate a branch view based on a virtual stream; the mapping itself refers to the underlying real stream.

-l

Long form: include full text of the changelist description.

-r

Reverse source and target (that is, reverse the direction of the integration).

-S stream [-P parent]

Display integrations pending between the stream and its parent. To treat another stream as the parent, specify -P.

-t

Display full date and time that changelist was submitted. By default, only the date is displayed.

-u user

Limit results to those submitted by the specified user.

g-opts

See “Global Options”.

Usage Notes

Can File Arguments Use Revision Specifier?

Can File Arguments Use Revision Range?

Minimal Access Level Required

N/A

N/A

list