p4 label

Synopsis

Syntax

Description

Running p4 label merely lists the files that are allowed to be included in the label. You'll need to use p4 labelsync to store files within the label. Only the Owner: of a label may use p4 labelsync.

Form Fields

Field Name	Type	Description
Label:	Read-only	The label name as provided in the invoking command.
Owner:	Writable	The label's owner. By default, the user who created the label. Only the owner of a label may update its contents with p4 labelsync.
Update:	Read-only	The date the label specification was last modified.
Access:	Read-only	The date and time the label was last accessed, either via p4 labelsync on the label, or syncing a file with the label revision specifier @label.
Description:	Writable, optional	A description of the label's purpose. Optional.
Options:	Writable	locked or unlocked. If the label is locked, its contents can't be changed with p4 labelsync.
View:	Writable	A list of depot files that can be included in this label. No files are actually included until p4 labelsync is invoked. Unlike client views or branch views, which map one set of files to another, label views consist of a simple list of depot files. Please see the Views chapter for more information.

Options

-d [-f]	Delete the named label if it's unlocked. The -f flag forces the deletion even if the label is locked.
-i	Read the label definition from standard input without invoking the editor.
-o	Write the label definition to standard output without invoking the editor.
-f	Allows the Update: field's date to be set. Can be used with either the -i flag or the -t flag for the same purpose.
-t template	Copy label template's view into the View: field of this 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
N/A	N/A	open

Related Commands

To include client workspace files in a label	p4 labelsync
To list all labels known to the system	p4 labels