p4 tag

Synopsis

Tag files with a label.

Syntax

p4 [g-opts] tag [-d -g -n -U] -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

-d

Delete the label tag from the named files.

-g

In distributed environments, use the -g flag to specify whether the label being applied is local to an edge server, or is globally available from the commit server. To update a global label, the client workspace must also be an unbound (global) workspace.

-n

Display what p4 tag would do without actually performing the operation.

-l labelname

Specify the label to be applied to file revisions

-U

If tagging files with a new label, set the unload option of the newly-created label. This option has no effect when used with an existing label.

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

list

  • 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.

  • With a distributed Perforce service, p4 labelsync works with a label local to the edge server. The -g flag can be used to apply a global label, but only with an unbound (global) client workspace.

    By default, labels are local to your edge server, and you use the -g flag to access global labels on the commit server. If your administrator has set rpc.labels.global to 1, labels are global by default, and the meaning of the -g flag is inverted to allow updating of local labels.

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 build.

If the label build 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

Hide partial matches
Highlight matches
0 matching pages