p4 resubmit
Resolve and resubmit some or all unsubmitted changes.
For distributed version control only:
- You can issue this command directly to a commit server.
- You CANNOT issue this command directly to an edge server.
- See Using Helix Core Server for Distributed Versioning.
Syntax
p4 [g-opts] resubmit -l
p4 [g-opts] [-R] resubmit -m
p4 [g-opts] [-R] resubmit -e
p4 [g-opts] [-R] resubmit -i [[-r remote] filespec ...]
Description
The p4 resubmit
command resubmits changes that have
been unsubmitted. Use this command to revise a set of changelists that you have:
- submitted locally
- not pushed to any other server
- have unsubmitted
Options
|
Runs |
|
Runs |
|
Lists all the unsubmitted changes but takes no action. This is useful as a way to preview the work that must be resubmitted. |
|
Runs in automatic mode. The first thing $ p4 unshelve -s change -c change
$ p4 sync
$ p4 resolve -am
$ p4 shelve -d -c change
$ p4 submit -c change
If, for any change in the list, the |
|
When $ p4 resubmit -r rmt @>=17
This example affects only the files specific by the remote spec, not all files in the depot. |
|
Resume the resubmit process once conflicts have been resolved. With this flag, resubmit begins by submitting the fully-resolved change and then proceeds to the next unsubmitted change. |
|
When a filespec is provided with the |
Usage Notes
Can File Arguments Use Revision Specifier? | Can File Arguments Use Revision Range? | Minimal Access Level Required |
---|---|---|
N/A |
N/A |
write, |
Examples
|
Merges and resubmits your unsubmitted changes. |
Related Commands
To unsubmit submitted changelists |