p4 remote

Create, modify or delete a remote specification.

Note

For distributed version control. See Using Helix Core Server for Distributed Versioning.

Syntax

p4 [g-opts] remote [-f] remoteID
p4 [g-opts] remote -d [-f] remoteID
p4 [g-opts] remote -o remoteID
p4 [g-opts] remote -i [-f]

Description

A remote describes the shared server that your server cooperates with. The p4 remote command lets you configure your system to use the p4 fetch and p4 pull commands to copy work between your server and the shared server. A remote specification describes the high level configuration and usage of a remote. The p4 remote command allows you to create, modify, or delete a remote specification.

Note

These remotes have nothing to do with the Helix Server construct of remote depots.

The p4 remote command puts the remote specification (spec) into a temporary file and invokes the editor configured by the P4EDITOR environment variable. Saving the file creates or modifies the remote spec.

A remote spec contains the following fields:

Options

With no options specified, p4 remote invokes your editor for the specified remote spec.

-d remote

Deletes the named remote.

-f

Enables a user with admin privileges to delete the spec or set the last modified date. By default, specs can be deleted only by their owner.

-i

Causes a remote spec to be read from the standard input. The user’s editor is not invoked.

-o remote

Writes the remote spec for the named remote to standard output. The user’s editor is not invoked.

Usage Notes

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

N/A

N/A

open,
or list to use the -o option
or admin to use the -f option

Examples

p4 remote -i

Read in a remote spec from standard input.

Related Commands

To display a list of remote specifications

p4 remotes