Synchronize a label with the current client contents
p4 labelsync causes the named label to reflect the current contents of the client. It records the last revision of each file taken onto the client. The label's name can subsequently be used in a revision specification as @label to refer to the revision of a file as stored in the label.
Without a file argument, p4 labelsync causes the label to reflect the contents of the whole client, by adding, deleting, and updating the label. If a file is given, p4 labelsync updates only that named file. If the file argument includes a revision specification, then that revision is used instead of the revision taken by the client.
A label that has its Options: field set to locked cannot be updated with p4 labelsync.
| -a | Add files that match the file pattern arguments to the label without deleting any files, even if some of the files are deleted at their head revision. |
| -d | Delete the named files from the label. |
| -n | Display what p4 labelsync would do without actually performing the operation. |
| g_opts | See global options section. |
|
Can File Arg Use Revision Specifier? |
Can File Arg Use Revision Range? |
Minimal Access Level Required |
|---|---|---|
| Yes | No | open |