{"id":133,"date":"2026-10-12T11:22:23","date_gmt":"2026-10-12T11:22:23","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2009\/06\/20\/cheat-sheet-of-perforce-command-line\/"},"modified":"2026-10-12T11:22:23","modified_gmt":"2026-10-12T11:22:23","slug":"cheat-sheet-of-perforce-command-line","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/cheat-sheet-of-perforce-command-line\/","title":{"rendered":"Perforce p4 Command-Line Cheat Sheet: Query, Sync, Integrate, and Admin Workflows"},"content":{"rendered":"\n

Perforce command names can look similar when you are under delivery pressure. This updated cheat sheet helps developers, release engineers, and administrators quickly choose the right p4<\/code> command for searching history, syncing files, integrating codelines, and managing labels.<\/p>\n\n\n\n

Originally published on 2009-06-20; fully revised and updated.<\/em><\/p>\n\n\n\n

Original reference post: Perforce Web References & Cheatsheet<\/a>.<\/p>\n\n\n\n

\"perforce-command-line-cheatsheet\"\/<\/figure>\n\n\n\n

Command chooser for Perforce data-mining questions<\/h2>\n\n\n\n

When the question is clear, the command choice is usually straightforward. Use this mapping to decide whether you need file names, changelists, detailed history, or content differences.<\/p>\n\n\n\n

Question pattern<\/th>Start with<\/th>Example<\/th><\/tr><\/thead>
What are the filenames that match a path or revision?<\/td>p4 files<\/code> or p4 have<\/code><\/td>p4 files \/\/depot\/...#head<\/code>
p4 files \/\/depot\/...@label<\/code>
p4 have<\/code><\/td><\/tr>
What changed in my workspace copy versus depot?<\/td>p4 diff<\/code><\/td>p4 diff file.c<\/code>
p4 diff -se<\/code><\/td><\/tr>
What differs between two depot files, paths, or revisions?<\/td>p4 diff2<\/code><\/td>p4 diff2 file1.c#1 file1.c#2<\/code>
p4 diff2 dir1\/...@now dir1\/...@2000\/01\/02<\/code><\/td><\/tr>
Tell me everything about changelist N.<\/td>p4 describe<\/code><\/td>p4 describe 1231<\/code><\/td><\/tr>
Show changelists for a path, file, or integration history.<\/td>p4 changes<\/code><\/td>p4 changes \/\/depot\/eng\/prodxyz\/...<\/code>
p4 changes -i \/\/depot\/eng\/prodxyz\/...<\/code><\/td><\/tr>
Show all revisions and integrations of one file.<\/td>p4 filelog<\/code><\/td>p4 filelog file.java<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n
p4 files \/\/depot\/...#have<\/span>\np4 files \/\/depot\/...@1541<\/span>\np4 changes file.c\np4 describe 1231<\/span>\np4 filelog file.java<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Daily workspace workflow<\/h2>\n\n\n\n
This is the common developer loop: configure workspace, sync, open files, review, and submit.<\/p>\n\n\n\n
\nflowchart TD\n    A[Create or update workspace] --> B[Sync files from depot]\n    B --> C[Open files for add edit or delete]\n    C --> D[Review local changes]\n    D --> E{Ready to publish}\n    E -- no --> F[Continue editing or revert]\n    F --> C\n    E -- yes --> G[Submit changelist]\n    G --> H[Integrate or share with team]\n<\/pre>\n\n\n
p4 set<\/span> P4CLIENT=my_workspace\np4 client -t 1.0dev\np4 sync \/\/depot\/eng\/...\n\np4 edit relnotes.txt\np4 diff relnotes.txt\np4 submit relnotes.txt\n\np4 revert -a\np4 revert file.java<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Revision specifiers quick reference<\/h2>\n\n\n\n
Many Perforce commands become much more useful when you add a revision specifier.<\/p>\n\n\n\n
Specifier<\/th>Typical meaning in this cheat sheet<\/th>Example<\/th><\/tr><\/thead>
#head<\/code><\/td>Head revision of a file<\/td>p4 sync file.java#head<\/code><\/td><\/tr>
@now<\/code><\/td>Current state at the present time<\/td>p4 sync file.java@now<\/code><\/td><\/tr>
@YYYY\/MM\/DD<\/code><\/td>File state as of a date<\/td>p4 sync file.java@2000\/04\/15<\/code><\/td><\/tr>
@label<\/code><\/td>Revisions captured by a label<\/td>p4 sync file.java@xyz<\/code><\/td><\/tr>
@123456<\/code><\/td>Revisions as of a changelist<\/td>p4 sync file.java@123456<\/code><\/td><\/tr>
@client<\/code><\/td>Revision associated with a named client workspace<\/td>p4 sync file.java@jab.work<\/code><\/td><\/tr>
#have<\/code><\/td>Revision currently in your workspace<\/td>p4 sync -f file.java#have<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Branching and selective integration<\/h2>\n\n\n\n
Use branch specifications consistently, then drive integrations with p4 integ<\/code> (shorthand for p4 integrate<\/code>) and inspect branch differences with p4 diff2 -b<\/code>.<\/p>\n\n\n\n
Goal<\/th>Command pattern<\/th>Notes<\/th><\/tr><\/thead>
Push from base codeline to release codeline<\/td>p4 integ -b branchName [file\/revision args]<\/code><\/td>Use changelist ranges like \/\/...@129,@134<\/code> for selective pushes.<\/td><\/tr>
Push from release back to base<\/td>p4 integ -b branchName -r [file\/revision args]<\/code><\/td>-r<\/code> reverses source and target from the branch spec.<\/td><\/tr>
Compare branch spec source and target<\/td>p4 diff2 -b branchName<\/code><\/td>Useful before or after larger merges.<\/td><\/tr>
List available branch specs<\/td>p4 branches<\/code><\/td>Most useful when teams standardize branch spec naming.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n
# Base to release<\/span>\np4 integ -b prodxyz-1.0<\/span>.1<\/span> \/\/...@=1232<\/span>\np4 integ -b prodxyz-1.0<\/span>.1<\/span> \/\/...@129,@134<\/span>\np4 integ -b prodxyz-1.0<\/span>.1<\/span>\n\n# Release to base (reverse mapping from branch spec)<\/span>\np4 integ -b prodxyz-1.0<\/span>.1<\/span> -r @=1235<\/span>\np4 integ -b prodxyz-1.0<\/span>.1<\/span> -r \/\/...@127,@128<\/span>\np4 integ -b prodxyz-1.0<\/span>.1<\/span> -r\n\n# Branch comparison<\/span>\np4 diff2 -b prodxyz-1.0<\/span>.1<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Labels and release snapshots<\/h2>\n\n\n\n
Labels provide a named snapshot of file revisions. The original cheat sheet uses a two-step pattern: create label metadata, then populate label contents.<\/p>\n\n\n
# Create and populate a label<\/span>\np4 label xxx\np4 labelsync -l xxx\np4 labelsync -l xxx file1 file2\n\n# Copy one label's contents into a new label<\/span>\np4 label -t xxx abc\np4 labelsync -l abc \/\/...@xxx<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Working offline and reconciling later<\/h2>\n\n\n\n
The original guide includes a practical recovery pattern for edits made while disconnected: detect edits, deletions, and additions, then open files in Perforce accordingly.<\/p>\n\n\n
p4 diff -se | p4 -x - edit\np4 diff -sd | p4 -x - delete<\/span>\nfind . -type f -print | p4 -x - add\n\np4 opened\np4 diff<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Administration commands from the original sheet<\/h2>\n\n\n\n
Command<\/th>Use<\/th>Access level<\/th><\/tr><\/thead>
p4 admin checkpoint<\/code><\/td>Create a checkpoint<\/td>Administrator (super)<\/td><\/tr>
p4 protect<\/code><\/td>Edit protections\/permissions<\/td>Administrator<\/td><\/tr>
p4 protects<\/code><\/td>Show effective permissions<\/td>Any user with command access<\/td><\/tr>
p4 client<\/code> (set compress<\/code>)<\/td>Enable client-side network compression in workspace options<\/td>Workspace owner<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Best practices and common pitfalls<\/h2>\n\n\n\n
  • Check before submit:<\/strong> run p4 opened<\/code> and p4 diff<\/code> so your changelist contains only intended files.<\/li>
  • Use p4 revert<\/code> carefully:<\/strong> the original sheet explicitly warns it is irreversible for unopened\/unsubmitted work.<\/li>
  • Be cautious with selective integrations:<\/strong> review merge choices carefully, especially when reversing flow with -r<\/code>.<\/li>
  • Standardize branch specs:<\/strong> consistent naming makes p4 integ -b ...<\/code> and p4 diff2 -b ...<\/code> much safer to reuse.<\/li>
  • Verify behavior against your installed Perforce version:<\/strong> some notes in the 2009-era sheet reference older releases and may differ in modern environments.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
    A practical Perforce CLI reference for choosing the right p4 command quickly. Covers data-mining commands, workspace flow, revision syntax, branching, labels, and admin tasks.<\/p>\n","protected":false},"author":1,"featured_media":4061,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[370],"tags":[3203,824,3206,384,3210,3211,3209,2837,373,3207,3204,3205,3213,3217,3216,3214,3215,3212,3208],"class_list":["post-133","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-perforce","tag-cheat-sheet","tag-command-line","tag-data-mining-commands","tag-p4","tag-p4-changes","tag-p4-filelog","tag-p4-files","tag-p4v","tag-perforce","tag-perforce-command-reference","tag-perforce-command-line","tag-perforce-command-line-cheat-sheet","tag-perforce-command-line-guide","tag-perforce-command-line-help","tag-perforce-command-line-list","tag-perforce-command-line-reference","tag-perforce-command-line-resource","tag-perforce-command-line-tutorial","tag-reference-guide"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/133","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=133"}],"version-history":[{"count":3,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/133\/revisions"}],"predecessor-version":[{"id":78982,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/133\/revisions\/78982"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media\/4061"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=133"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=133"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=133"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}