Perforce 2000.2 Command Reference (2000.2.cr.1) | ||
<< Previous Chapter p4 labels |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 lock |
Without a file argument, p4 labelsync causes the label to reflect the contents of the whole client, by adding, deleting, and updating the list of files in 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 existing in the client. If the file argument includes a revision range, then only the highest revision in that range is used.
You can only update labels you own; if the label's Owner: field is not your userid, it cannot be updated with p4 labelsync.
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. |
See the Global Options section. |
Perforce 2000.2 Command Reference (2000.2.cr.1) | ||
<< Previous Chapter p4 labels |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 lock |