Previous Table of Contents Index Next
Perforce 2009.2: Command Reference



p4 tag
Synopsis
Tag files with a label.
Syntax
p4 [g-opts] tag [ -d -n ] -l labelname file[revRange]...
Description
Use p4 tag to tag specified file revisions with a label. A labelname is required. If a label named labelname does not exist, it is created automatically. If the label already exists, you must be the Owner: of the label and the label must be unlocked in order for you to tag or untag files with the label. (Use p4 label to change label ownership or lock status.)
If the file argument does not include a revision specification, the head revision is tagged with the label. If the file argument includes a revision range specification, only files with revisions in that range are tagged. (If more than one revision of the file exists in the specified range, the highest revision in the specified range is tagged.)
Options
Display what p4 tag would do without actually performing the operation.
-l labelname
Usage Notes
Can File Arguments Use
Revision Specifier?
By default, p4 tag operates on the head revision of files in the depot. To preserve the state of a client workspace, use p4 labelsync, which operates on the revision of files last synced to your workspace.
Examples
Tag the head revisions of files in //depot/1.0/... with label rel1.
If the label rel1 does not exist, create it.
Tag the most recent revisions as of the submission of changelist 1234 of files in //depot/1.0/... with label build.
If the label build does not exist, create it.
Related Commands
 


Previous Table of Contents Index Next

Perforce 2009.2: Command Reference
Copyright 1999-2009 Perforce Software.