Provides information about why a file is being ignored during add and reconcile operations. Using this command allows you to see the ignore rules that are applied for any given path.

See “Environment and Registry Variables” for more information.

If the API level is 79 or greater, canonical filetypes are now displayed by default for all commands that display filetypes. If the API level is 78 or lower, filetype aliases are displayed instead. If your script depends on the display of filetype aliases, you will need either to change the api level or to change your script.

The use of the new-u option allows you to display the name of the user who modified the change and the date when the modification occurred.

The addition of the --serverid option prevents you from forcibly removing a changelist that is on another server.

Includes a new -e changelist# option to display only changes that are greater or equal to the specified changelist number.

The addition of the --serverid option prevents you from forcibly removing a client that is connected to another server.

You can now create a depot of type tangent. The depot spec has also added the field StreamDepth that you can use to specify the subdirectory level where you can root streams in a stream-type depot.

The -S option is now optional. If you specify no arguments for p4 diff2, the current stream is diffed against its parent stream.

In addition to copying files, p4 fetch also copies any revision attributes and fix records.

p4 fetch now takes a -t option, which specifies that conflicting changes should be unsubmitted and moved into a tangent in the tangent depot, automatically creating that depot if it doesn't exist.

This command now runs in lockless mode if db.peeking is set to 3.

This command now returns information about the services offered by the current server and specifies which server this server replicates if this server is a replica.

The owner of a label may be a group.

This command may not be run from a read-only or build replica. New attributes have been added to the LDAP spec.

LDAP configurations are stored in the new db.ldap table. This table is journalled, so LDAP configurations are now included in checkpoints and are replicated.

You can use the [no]downcase option in the LDAP spec options field to specify whether p4 ldapsync should downcase user names (found by the group query) when updating user names.

Login attempts, whether successful or not, are logged to a structured log file. If the login fails, the reason for failure is included in the log. In the case of authentication triggers or LDAP authentication, the parts of the error message that contain user data are sanitized as needed.

You can now specify the remote server to which the login should be forwarded, with the new -r option.

In an edge/commit architecture, use the new -g flag to lock the files locally and globally. This option may only be used from an edge server, and it must be used with the -c changelist option.

Login attempts, whether successful or not, are logged to a structured log file. If the login fails, the reason for failure is included in the log. In the case of authentication triggers or LDAP authentication, the parts of the error message that contain user data are sanitized as needed.

More precise information about a replica's use of pull threads is now available.

A new --batch option allows you to specify the number of files that can be fetched by one pull operation. This might improve performance if you are pulling many small files.

In addition to copying files, p4 push also copies any revision attributes and fix records.

Use the new -k option to update the have list if files are mapped in a client's workspace to files in the depot that are not on the have list.

You can specify the identity (user) the Helix Versioning Engine will use to authenticate against a remote server when pushing and fetching, using the new RemoteUser field.

You may not issue this command directly to an edge server; you can issue it directly to a commit server.

You can leave the Name: field blank in the server specification, or you can set it to the same value as serverid.

When you run this command, in addition to any open files being shelved, now any open stream specification will also be shelved.

You may now isolate edits to the stream spec to your client only and then make them available to other clients as part of an atomic changelist submission, using the new p4 stream edit, p4 stream resolve, and p4 stream revert commands.

You no longer have to pass in a stream name. By default, p4 stream edits your current stream, that is, the stream associated with your current workspace.

You can set the net.parallel.max, net.parallel.submit.threads, net.parallel.submit.min, and net.parallel.submit.batch configurables to automate parallel processing. In this case, you can use any of the syntax variants for the p4 submit command (without specifying the --parallel option) and processing will be automatically done in parallel.

When you run this command, in addition to any open files being submitted, now any open stream specification will also be submitted.

This command can now take stream@change argument to generate a workspace view from a stream’s particular version.

Defaults for --parallel option values have changed.

Journal-rotate and push triggers have been added.

Defaults for --parallel option values have changed.

Use the new -p option for promoting the shelves of unloaded clients.

An administrator can now remove unwanted orphaned locked files.

In an edge/commit architecture, use the new -g flag to unlock the files locally and globally. This option may only be used from an edge server, and it must be used with the -c changelist option.

You may unshelve a promoted shelf into open files and branches on a server from where the shelf did not originate.

When you run this command, in addition to any shelved files being unshelved, now any shelved stream specification will also be shelved.

You may not issue this command directly to an edge server; you can issue it directly to a commit server.

In addition to copying files, p4 unzip also copies any revision attributes and fix records.

A new option allows you to enable push triggers for the p4 unzip command.

A new -S option allows you to verify shelved files.

The existing -t option may now be used for replicas that have lbr.replication=cache set.

In addition to copying files, p4 zip also copies any revision attributes and fix records.

The addition of the type field allows you to create a read-only client that can be used for automated testing.

The addition of the backup field allows you to disable the backup of a particular client connected to a cluster workspace.

New fields include LdapConfig, LdapSearchQuery, and LdapUserAttribute. These are used with the p4 ldapsync command.

New field to specify a remote user.

New optional field ExternalAddress specifies the external address used for connections to a commit server. This field must be set for the edge server to enable parallel submits in a federated environment.

Set this configurable to the path were db.* files will be placed for a read-only client.

You can set the net.parallel.max, net.parallel.submit.threads, net.parallel.submit.min, and net.parallel.submit.batch configurables to automate parallel processing. In this case, you can use any of the syntax variants for the p4 submit command (without specifying the --parallel option) and processing will be automatically done in parallel.

Specifies one or more clients whose requests should be blocked. For more information, see "Rejecting client connection requests" in Helix Versioning Engine Administrator Guide: Fundamentals.

Set to 1 to replicate the db.user.rp table. See “Configurables” for more information.

Controls whether the view maps of a non-stream client on an edge server or workspace server are made global when a client is modified. See also "Setting global client views" in Helix Versioning Engine Administrator Guide: Multi-site Deployment.

Can now inherit any extra settings specified in P4CONFIG files in subdirectories.

Can be set to a list of files rather than a single file. Syntax rules for ignore files have also changed.

Can no longer be set globally; you must specify a server id.

Can no longer be set globally; you must specify a server id.

Can no longer be set globally; you must specify a server id.

The default length of the queue has been increased to 128 connections.

A new value of 4 allows you to compress only the journal pull and journal copy connections between the replica and the master.