Perforce Table of Contents
Concepts
- Overview
- Architecture
- Moving Files Between the Clients and the Server
- File Conflicts
- Labeling Groups of Files
- Branching Files
- Job Tracking
- Change Review, Daemons, and Triggers
- Protections
Connecting to the Perforce Server
Quick Start
- Overview
- Concepts
- Setting up a client workspace
- Copying depot files into your workspace
- Updating the depot with files from your workspace
- Backing out: reverting files to their unopened states
- Basic reporting commands
The Details
- Overview
- Description of the Client Workspace
- Wildcards
- Mapping the Depot to the Client Workspace
- Editing Existing Client Specifications
- Referring to Files on the Command Line
- Name and String Limitations
- Specifying Older File Revisions
- Revision Ranges
- File Types
- Forms and Perforce Commands
- General Reporting Commands
Resolving File Conflicts
- Overview
- RCS Format: How Perforce Stores File Revisions
- Scheduling Resolves of Conflicting Files
- Why "p4 sync" to Schedule a Resolve?
- How Do I Know When a Resolve is Needed?
- Performing Resolves of Conflicting Files
- Using Flags with Resolve to Automatically Accept Particular Revisions
- Locking Files to Minimize File Conflicts
- Resolves and Branching
- Resolve Reporting
Miscellaneous Topics
- Overview
- Reconfiguring the Perforce Environment with $P4CONFIG
- Perforce Passwords
- Command-Line Flags Common to All Perforce Commands
- Working Detached
- Refreshing files
- Recommendations for Organizing the Depot
- Renaming Files
Changelists
- Overview
- Working with the Default Changelist
- Creating Numbered Changelists Manually
- Working With Numbered Changelists
- Automatic Creation and Renumbering of Changelists
- Perforce May Renumber a Changelist upon Submission
- Deleting Changelists
- Changelist Reporting
Labels
- Overview
- Why Not Just Use Changelist Numbers?
- Creating a Label
- Adding and Changing Files Listed in a Label
- Preventing Accidental Overwrites of a Label's Contents
- Retrieving a Label's Contents into a Client Workspace
- Deleting Labels
- Label Reporting
Branching
- Overview
- What is Branching?
- When to Create a Branch
- Perforce's Branching Mechanisms: Introduction
- Branching and Merging, Method 1: Branching with File Specifications
- Branching and Merging, Method 2: Branching with Branch Specifications
- Branch Specification Usage Notes
- Integration Usage Notes
- Deleting Branches
- Advanced Integration Functions
- How Integrate Works
- Integration Reporting
- For More Information
Job Tracking
- Overview
- Job Usage Overview
- Viewing jobs by content with jobviews
- Linking Jobs to Changelists
- Deleting Jobs
- Integrating with External Defect Tracking Systems
- Job Reporting Commands
Reporting and Data Mining
- Overview
- Changelists
- Labels
- Branch and Integration Reporting
- Job Reporting
- Reporting for Daemons
- System Configuration
- Special Reporting Flags
- Reporting with Scripting
Installing Perforce
- Getting Perforce
- Installing Perforce on UNIX
- Download the files and make them executable
- Creating a Perforce server root directory
- Telling the Perforce server which port to listen to
- Starting the Perforce server
- Stopping the Perforce server
- Telling Perforce clients which port to talk to
- Installing Perforce on Windows
- Terminology note: Windows services and servers
- Starting and stopping Perforce on Windows
Environment Variables
- Setting and viewing environment variables
![]()