p4 tag

Synopsis

Syntax

Description

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

-d	Delete the label tag from the named files.
-n	Display what p4 tag would do without actually performing the operation.
-l labelname	Specify the label to be applied to file revisions
g-opts	See the Global Options section.

Usage Notes

Can File Arguments Use Revision Specifier?	Can File Arguments Use Revision Range?	Minimal Access Level Required
Yes	Yes	open

• 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

p4 tag -l rel1 //depot/1.0/...	Tag the head revisions of files in //depot/1.0/... with label rel1. If the label rel1 does not exist, create it.
p4 tag -l build //depot/1.0/...@1234	Tag the most recent revisions as of the submission of changelist 1234 of files in //depot/1.0/... with label rel1. If the label rel1 does not exist, create it.
p4 files @labelname	List the file revisions tagged by labelname.

Related Commands

To create or edit a label	p4 label
To list all labels known to the system	p4 labels
To tag revisions in your client workspace with a label	p4 labelsync
To create a label and tag files with the label	p4 tag