p4 populate
Synopsis
Branch a set of files as a one-step operation.
Syntax
p4 [g-opts
] populate [-ddescription
] [-f -n -o] [-mmax
]fromFile
[rev
]toFile
p4 [g-opts
] populate [-ddescription
] [-f -n -o] [-mmax
] -bbranch
[-r] [toFile
[rev]] p4 [g-opts
] populate [-ddescription
] [-f -n -o] [-mmax
] -bbranch
-sfromFile
[rev
] [toFile
] p4 [g-opts
] populate [-ddescription
] [-f -n -o] [-mmax
] -Sstream
[-Pparent
] [-r] [toFile
[rev
]]
Description
The p4 populate
command branches a set of files (the source)
into another depot location (the target) in a single step. The new files
are created immediately, without requiring a p4
submit
or a client workspace.
The execution of the p4 populate
command now fires a
change-submit
trigger to allow interested parties to perform some
validation before submission. As with change-content triggers, a
temporary pending change record is created so that the description can
be accessed, but no results are returned to change-submit
triggers
from p4 opened
because files branched with p4
populate
are never opened. If no description is given, the command
line arguments are used for a description.
If the p4 populate
command fails after the change-content
stage succeeds, a change-fail
trigger is enabled.
The value of the rpl.checksum.change
configurable will determine the
level of verification performed for this command.
Options
|
Use the view in a user-defined |
|
Provide a description for the automatically-submitted changelist. If no description is provided, the command line arguments are used for a description. |
|
Force deleted files to be branched into the target. (By default, deleted files are treated as nonexistent and are skipped.) |
|
Limit the action to the first |
|
Preview the operation without actually doing anything. |
|
Display a list of files created by the |
|
When used with |
|
Reverse direction of integration (from target to source, rather than from source to target) |
|
If used with |
|
Use a stream’s view; the source is the stream itself, and the target is the stream’s parent. |
|
See “Global Options”. |
Usage Notes
Can File Arguments Use Revision Specifier? | Can File Arguments Use Revision Range? | Minimal Access Level Required |
---|---|---|
Yes |
No |
|