-e

Runs p4 resubmit in partially-interactive mode, allowing you to inspect each change prior to submitting it.

-i

Runs p4 resubmit as a fully interactive resubmission tool.

-l

Lists all the unsubmitted changes but takes no action. This is useful as a way to preview the work that must be resubmitted.

-m

Runs in automatic mode. The first thing p4 resubmit -m does is to sync your workspace to #head. Then, p4 resubmit -m processes each unsubmitted change, doing the following for each change:

$ 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 p4 resolve -am processing detects merge conflicts in any file in that change, the p4 resubmit command terminates at that point. All the files in that change which had merge conflicts are left unresolved. You must then run the p4 resolve command to resolve the conflicts. Then re-run p4 resubmit -Rm to resume the resubmit process (the first thing it does is submit the resolved files from this change, then it proceeds to the next change).

-r remote

When p4 resubmit is run with the -i option, the -r option specifies the remote spec whose mapping is used to limit the files affected by the unsubmit operation. For example:

$ p4 resubmit -r rmt @>=17

This example affects only the files specific by the remote spec, not all files in the depot.

-R

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.

filespec

When a filespec is provided with the -i option, the interactive resubmit first unsubmits each change that modified a file in that path.

N/A

N/A

write,
or admin to use the -i option

p4 resubmit -m

Merges and resubmits your unsubmitted changes.

To unsubmit submitted changelists

p4 unsubmit