@pv@ 0 @db.message@ @en@ 1076039681 @End of input in middle of word!@ @pv@ 0 @db.message@ @en@ 1076039682 @Word too big for buffer!@ @pv@ 0 @db.message@ @en@ 1076039683 @Octet stream too long!@ @pv@ 0 @db.message@ @en@ 1076039684 @Octet stream size mismatch!@ @pv@ 0 @db.message@ @en@ 1076039685 @Word too big for a number!@ @pv@ 0 @db.message@ @en@ 1092816902 @Bad quoting in journal file at line %line%!@ @pv@ 0 @db.message@ @en@ 1092816903 @Bad opcode '%operation%' journal record!@ @pv@ 0 @db.message@ @en@ 1076039688 @Missing version number in journal record!@ @pv@ 0 @db.message@ @en@ 1076039689 @Missing table name in journal record!@ @pv@ 0 @db.message@ @en@ 1076039690 @Missing table version in journal record!@ @pv@ 0 @db.message@ @en@ 1076039691 @Record version not known in journal record!@ @pv@ 0 @db.message@ @en@ 1076039692 @Journal record replay failed!@ @pv@ 0 @db.message@ @en@ 555945997 @Journal file '%file%' skipped (out of sequence).@ @pv@ 0 @db.message@ @en@ 1109594126 @Journal file '%file%' replay failed at line %line%!@ @pv@ 0 @db.message@ @en@ 1076039756 @Bad transaction marker!@ @pv@ 0 @db.message@ @en@ 1109594192 @Case-handling mismatch: server uses %caseUsage% but journal flags are %flags%!@ @pv@ 0 @db.message@ @en@ 301994065 @Server version %serverVersion% is replaying a version %journalVersion% journal.@ @pv@ 0 @db.message@ @en@ 838864978 @Server version %serverVersion% cannot replay a version %journalVersion% journal.@ @pv@ 0 @db.message@ @en@ 1092816911 @Database open error on %table%!@ @pv@ 0 @db.message@ @en@ 1092685840 @dbput %table%: no write lock!@ @pv@ 0 @db.message@ @en@ 1092685841 @Database write error on %table%!@ @pv@ 0 @db.message@ @en@ 1092685842 @dbget %table%: no read lock!@ @pv@ 0 @db.message@ @en@ 1092685843 @Database get error on %table%!@ @pv@ 0 @db.message@ @en@ 1076039700 @Database must be 98.1 through 2010.2 format.@ @pv@ 0 @db.message@ @en@ 1109463061 @dbget: %table% record format %level% unsupported!@ @pv@ 0 @db.message@ @en@ 1092685846 @dbscan %table%: no read lock!@ @pv@ 0 @db.message@ @en@ 1092685847 @Database scan error on %table%!@ @pv@ 0 @db.message@ @en@ 1109463064 @dbscan: %table% record format %level% unsupported!@ @pv@ 0 @db.message@ @en@ 1092685849 @dbdel %table%: no write lock!@ @pv@ 0 @db.message@ @en@ 1092685850 @Database delete error on %table%!@ @pv@ 0 @db.message@ @en@ 1092685851 @Database locking error on %table%!@ @pv@ 0 @db.message@ @en@ 1092685852 @End xact with %table% still locked!@ @pv@ 0 @db.message@ @en@ 1092685888 @GetDb of %table% without prior get!@ @pv@ 0 @db.message@ @en@ 822153245 @Table %table% not known.@ @pv@ 0 @db.message@ @en@ 822153294 @Table %table% is obsolete.@ @pv@ 0 @db.message@ @en@ 1109463070 @Locking failure: %table% locked after %table2%!@ @pv@ 0 @db.message@ @en@ 1092685855 @Locking failure: no upgrading %table%'s lock!@ @pv@ 0 @db.message@ @en@ 1093079073 @Request too large for server memory (try later?).@ @pv@ 0 @db.message@ @en@ 1075908642 @Record key exceeds max size!@ @pv@ 0 @db.message@ @en@ 822153251 @Only three ... permitted in '%arg%'.@ @pv@ 0 @db.message@ @en@ 822153252 @Too many *'s in '%arg%'.@ @pv@ 0 @db.message@ @en@ 822153253 @Duplicate wildcards in '%arg%'.@ @pv@ 0 @db.message@ @en@ 838930470 @Incompatible wildcards '%arg%' <-> '%arg2%'.@ @pv@ 0 @db.message@ @en@ 807866441 @Excessive combinations of wildcard ... in path and maps.@ @pv@ 0 @db.message@ @en@ 807866447 @Excessive combinations of wildcards in path and maps.@ @pv@ 0 @db.message@ @en@ 807866442 @Senseless juxtaposition of wildcards in '%arg%'.@ @pv@ 0 @db.message@ @en@ 822153257 @Expression parse error at '%line%'.@ @pv@ 0 @db.message@ @en@ 822153258 @Too many entries for field '%field%'.@ @pv@ 0 @db.message@ @en@ 838930475 @Value for field '%field%' must be one of %text%.@ @pv@ 0 @db.message@ @en@ 822153260 @Wrong number of words for field '%field%'.@ @pv@ 0 @db.message@ @en@ 822153261 @Missing required field '%field%'.@ @pv@ 0 @db.message@ @en@ 805376046 @Can't find numbered field in spec.@ @pv@ 0 @db.message@ @en@ 822153263 @Unknown field name '%field%'.@ @pv@ 0 @db.message@ @en@ 838930480 @Unknown type '%type%' for field '%field%'.@ @pv@ 0 @db.message@ @en@ 838930481 @Unknown option '%option%' for field '%field%'.@ @pv@ 0 @db.message@ @en@ 822153279 @No matching end quote in '%value%'.@ @pv@ 0 @db.message@ @en@ 822153266 @Syntax error in '%value%'.@ @pv@ 0 @db.message@ @en@ 822153267 @Error detected at line %line%.@ @pv@ 0 @db.message@ @en@ 807604276 @License expired.@ @pv@ 0 @db.message@ @en@ 807604277 @Support expired.@ @pv@ 0 @db.message@ @en@ 807604278 @Server newer than current date.@ @pv@ 0 @db.message@ @en@ 807604279 @License must expire.@ @pv@ 0 @db.message@ @en@ 807604280 @Invalid checksum string.@ @pv@ 0 @db.message@ @en@ 824381497 @This server is only licensed for %users% use.@ @pv@ 0 @db.message@ @en@ 807735354 @Can't have platforms for pre-97.2 servers.@ @pv@ 0 @db.message@ @en@ 807604283 @Error reading license file.@ @pv@ 0 @db.message@ @en@ 807604284 @License file invalid.@ @pv@ 0 @db.message@ @en@ 807604299 @Server license IPaddress changed, cannot proceed.@ @pv@ 0 @db.message@ @en@ 807604307 @License needs an application.@ @pv@ 0 @db.message@ @en@ 1075908674 @BTree is corrupt!@ @pv@ 0 @db.message@ @en@ 1075908675 @BTree could not be opened or created!@ @pv@ 0 @db.message@ @en@ 1075908676 @Internal BTree usage is not supported!@ @pv@ 0 @db.message@ @en@ 1075908677 @Allocation failure in db!@ @pv@ 0 @db.message@ @en@ 1075908678 @BTree variation is not supported!@ @pv@ 0 @db.message@ @en@ 1075908679 @Internal BTree system failure!@ @pv@ 0 @db.message@ @en@ 807866440 @MapCheck rejected too many rows.@ @pv@ 0 @db.message@ @en@ 1075908685 @BTree Case Order Mismatch! Check p4d -Cx flag usage.@ @pv@ 0 @db.message@ @en@ 824381472 @Request too large (over %maxResults%); see 'p4 help maxresults'.@ @pv@ 0 @db.message@ @en@ 824381501 @Too many rows scanned (over %maxScanRows%); see 'p4 help maxscanrows'.@ @pv@ 0 @db.message@ @en@ 839061543 @Path '%path%' is not under client's root '%root%'.@ @pv@ 0 @db.message@ @en@ 839061544 @Path '%path%' is not under client '%client%'.@ @pv@ 0 @db.message@ @en@ 1076039742 @Client has dropped connection, terminating request.@ @pv@ 0 @db.message@ @en@ 1076039742 @Command has been cancelled, terminating request.@ @pv@ 0 @db.message@ @en@ 335548481 @--- %table% pos %position% get %get% scan %scan%@ @pv@ 0 @db.message@ @en@ 841029633 @%table%/%table2% inconsistencies found.@ @pv@ 0 @db.message@ @en@ 838932482 @Invalid %type% '%arg%'.@ @pv@ 0 @db.message@ @en@ 805378051 @Identifiers too long. Must not be longer than 1024 bytes of UTF-8.@ @pv@ 0 @db.message@ @en@ 822155268 @Initial dash character not allowed in '%id%'.@ @pv@ 0 @db.message@ @en@ 805378053 @Empty identifier not allowed.@ @pv@ 0 @db.message@ @en@ 822155270 @Non-printable characters not allowed in '%id%'.@ @pv@ 0 @db.message@ @en@ 822155271 @Revision chars (@@, #) not allowed in '%id%'.@ @pv@ 0 @db.message@ @en@ 822155272 @Slashes (/) not allowed in '%id%'.@ @pv@ 0 @db.message@ @en@ 822155749 @Commas (,) not allowed in '%id%'.@ @pv@ 0 @db.message@ @en@ 822155273 @Null directory (//) not allowed in '%id%'.@ @pv@ 0 @db.message@ @en@ 822155274 @Relative paths (., ..) not allowed in '%id%'.@ @pv@ 0 @db.message@ @en@ 822155275 @Wildcards (*, %%%%x, ...) not allowed in '%id%'.@ @pv@ 0 @db.message@ @en@ 822155276 @Purely numeric name not allowed - '%id%'.@ @pv@ 0 @db.message@ @en@ 838932493 @Invalid option '%option%' in %field% option field.@ @pv@ 0 @db.message@ @en@ 822155278 @Invalid changelist number '%change%'.@ @pv@ 0 @db.message@ @en@ 822155279 @Invalid maximum value '%value%'.@ @pv@ 0 @db.message@ @en@ 822155686 @Invalid Timeout value '%value%'.@ @pv@ 0 @db.message@ @en@ 822155281 @Invalid revision number '%rev%'.@ @pv@ 0 @db.message@ @en@ 822155282 @Invalid file type modifier on '%arg%'; see 'p4 help filetypes'.@ @pv@ 0 @db.message@ @en@ 822155283 @Only one storage modifier +C +D +F or +S allowed on '%arg%'.@ @pv@ 0 @db.message@ @en@ 822155724 @Bad version count '+S%count%', only values 1-10,16,32,64,128,256,512 allowed.@ @pv@ 0 @db.message@ @en@ 838932500 @Disallowed modifier (%option%) on '%arg%'; see 'p4 help filetypes'.@ @pv@ 0 @db.message@ @en@ 822155285 @Invalid file type '%type%'; see 'p4 help filetypes'.@ @pv@ 0 @db.message@ @en@ 822155682 @Invalid digest string '%digest%'.@ @pv@ 0 @db.message@ @en@ 822155699 @A partial file type is not allowed here.@ @pv@ 0 @db.message@ @en@ 841160726 @Database is at old upgrade level %level%. Use 'p4d -xu' to upgrade to level %level2%.@ @pv@ 0 @db.message@ @en@ 841160727 @Database is at upgrade level %level% past this server's level %level2%.@ @pv@ 0 @db.message@ @en@ 824383512 @Database has %value% tables with non-UTF8 text and can't be switched to Unicode mode.@ @pv@ 0 @db.message@ @en@ 1092687897 @%key% description missing!@ @pv@ 0 @db.message@ @en@ 822220826 @%change% unknown.@ @pv@ 0 @db.message@ @en@ 822286363 @%change% is already committed.@ @pv@ 0 @db.message@ @en@ 839063580 @%change% belongs to client %client%.@ @pv@ 0 @db.message@ @en@ 839063581 @%change% belongs to user %user%.@ @pv@ 0 @db.message@ @en@ 822220830 @No such counter '%counter%'.@ @pv@ 0 @db.message@ @en@ 822155295 @Too dangerous to touch counter '%counter%'.@ @pv@ 0 @db.message@ @en@ 822220832 @Depot '%depot%' doesn't exist.@ @pv@ 0 @db.message@ @en@ 822220833 @Depot '%depot%' unknown - use 'depot' to create it.@ @pv@ 0 @db.message@ @en@ 838998050 @%type% '%name%' doesn't exist.@ @pv@ 0 @db.message@ @en@ 855775267 @%type% '%name%' unknown - use '%command%' command to create it.@ @pv@ 0 @db.message@ @en@ 855840804 @%name% is a %type%, not a %type2%.@ @pv@ 0 @db.message@ @en@ 807606309 @Can't add client - over license quota.@ @pv@ 0 @db.message@ @en@ 822220838 @Job '%job%' doesn't exist.@ @pv@ 0 @db.message@ @en@ 822220839 @Job '%job%' unknown - use 'job' to create it.@ @pv@ 0 @db.message@ @en@ 805443624 @No such fix.@ @pv@ 0 @db.message@ @en@ 805705769 @You don't have permission for this operation.@ @pv@ 0 @db.message@ @en@ 822155801 @There was no Perforce release named '%release%'.@ @pv@ 0 @db.message@ @en@ 822155802 @You may not set minClient to a release newer than your client.@ @pv@ 0 @db.message@ @en@ 822483067 @Access for user '%user%' has not been enabled by 'p4 protect'.@ @pv@ 0 @db.message@ @en@ 839063594 @Path '%depotFile%' is not under '%prefix%'.@ @pv@ 0 @db.message@ @en@ 807606315 @Can't create a new user - over license quota.@ @pv@ 0 @db.message@ @en@ 839063596 @Mapping '%depotFile%' is not under '%prefix%'.@ @pv@ 0 @db.message@ @en@ 805509552 @User does not have list access for mapped depots.@ @pv@ 0 @db.message@ @en@ 1092687917 @Depot %depot% missing from depot table!@ @pv@ 0 @db.message@ @en@ 1075910702 @Depot and domains table out of sync!@ @pv@ 0 @db.message@ @en@ 1075910703 @Revision table out of sync with index!@ @pv@ 0 @db.message@ @en@ 1092687920 @Can't find %depotFile%'s successor rev!@ @pv@ 0 @db.message@ @en@ 1092687921 @Can't find %change%!@ @pv@ 0 @db.message@ @en@ 1075910706 @DmtIntegData unknown DBT_OPEN_FLAG!@ @pv@ 0 @db.message@ @en@ 1075910707 @Job template unusable!@ @pv@ 0 @db.message@ @en@ 1076041780 @Jobs database must be upgraded with 'p4 jobs -R'!@ @pv@ 0 @db.message@ @en@ 1076041781 @Presets in jobspec unusable!@ @pv@ 0 @db.message@ @en@ 1076041782 @Missing job name field!@ @pv@ 0 @db.message@ @en@ 1092687927 @File %depotFile% isn't in revisions table!@ @pv@ 0 @db.message@ @en@ 1075910712 @DmOpenData unhandled DBT_OPEN_FLAG!@ @pv@ 0 @db.message@ @en@ 1092687929 @File %depotFile% changed it's name!@ @pv@ 0 @db.message@ @en@ 1075910714 @Working and locked tables out of sync!@ @pv@ 0 @db.message@ @en@ 1092687931 @%depotFile% is missing from the rev table!@ @pv@ 0 @db.message@ @en@ 1092687932 @%depotFile% is missing from the working table!@ @pv@ 0 @db.message@ @en@ 822417469 @%depotFile% has muddled resolve from 99.2; revert and retry (sorry).@ @pv@ 0 @db.message@ @en@ 805378110 @Change description missing. You must enter one.@ @pv@ 0 @db.message@ @en@ 807671871 @Invalid JobView. Set with 'p4 user'.@ @pv@ 0 @db.message@ @en@ 822286400 @Can't update committed change %change%.@ @pv@ 0 @db.message@ @en@ 805574721 @Client and status cannot be changed.@ @pv@ 0 @db.message@ @en@ 805575123 @Client, user, date and status cannot be changed.@ @pv@ 0 @db.message@ @en@ 805575129 @Change has files open, client cannot be modified.@ @pv@ 0 @db.message@ @en@ 805575165 @Change has files open, user cannot be modified.@ @pv@ 0 @db.message@ @en@ 805574722 @Can't include file(s) not already opened. Open new files with p4 add, p4 edit, etc.@ @pv@ 0 @db.message@ @en@ 822417475 @Depot %depot% isn't empty; clear it with 'p4 obliterate' first.@ @pv@ 0 @db.message@ @en@ 856037444 @Locked %type% '%name%' owned by '%user%'; use -f to force update.@ @pv@ 0 @db.message@ @en@ 839260230 @%type% '%name%' is locked and can't be deleted.@ @pv@ 0 @db.message@ @en@ 822417479 @Client '%client%' has files opened; use -f to force delete.@ @pv@ 0 @db.message@ @en@ 822417855 @Client '%client%' has pending changes; use -f to force delete.@ @pv@ 0 @db.message@ @en@ 822417932 @Client '%client%' has files shelved; use 'shelve -df' to remove them, and then try again.@ @pv@ 0 @db.message@ @en@ 822220872 @Group '%group%' doesn't exist.@ @pv@ 0 @db.message@ @en@ 805378469 @Overlay (+) mappings are not allowed in branch views.@ @pv@ 0 @db.message@ @en@ 805378496 @Havemap entries found in non-client view!@ @pv@ 0 @db.message@ @en@ 805378121 @Branch mapping produced illegal filename.@ @pv@ 0 @db.message@ @en@ 805378122 @The job name 'job' is reserved.@ @pv@ 0 @db.message@ @en@ 822155339 @'%field%' field blank. You must provide it.@ @pv@ 0 @db.message@ @en@ 805444018 @Job has been modified by another user, clear date field to overwrite.@ @pv@ 0 @db.message@ @en@ 838932921 @%field% is a read-only always field and can't be changed from '%value%'. The job may have been updated while you were editing.@ @pv@ 0 @db.message@ @en@ 822155676 @Unknown spec type %type%.@ @pv@ 0 @db.message@ @en@ 855710106 @Field codes must be between %low%-%hi% for %type% specs.@ @pv@ 0 @db.message@ @en@ 838932557 @%field% is read-only and can't be changed from '%value%'.@ @pv@ 0 @db.message@ @en@ 822155342 @%field% can't have a default multi-word value.@ @pv@ 0 @db.message@ @en@ 822155675 @Builtin field %code% cannot be changed.@ @pv@ 0 @db.message@ @en@ 839260240 @Can't modify label '%label%' owned by '%user%'.@ @pv@ 0 @db.message@ @en@ 822483025 @Can't modify locked label '%label%'. Use 'label' to change label options.@ @pv@ 0 @db.message@ @en@ 822417846 @Label '%label%' has a Revision field and must remain empty.@ @pv@ 0 @db.message@ @en@ 805378130 @Can't add filenames with wildcards [@@#%*] in them. Use -f option to force add.@ @pv@ 0 @db.message@ @en@ 805378481 @Target file has illegal escape sequence [%xx].@ @pv@ 0 @db.message@ @en@ 822155347 @Indicator must be 'user' or 'group', not '%value%'.@ @pv@ 0 @db.message@ @en@ 822155348 @User name can't be changed from '%user%'.@ @pv@ 0 @db.message@ @en@ 822155841 @User type can't be changed.@ @pv@ 0 @db.message@ @en@ 807737429 @You need a 98.2 or newer client to set a password.@ @pv@ 0 @db.message@ @en@ 805378467 @Passwords can only be set by 'p4 passwd' at this security level.@ @pv@ 0 @db.message@ @en@ 822483030 @Not user '%user%'; use -f to force delete.@ @pv@ 0 @db.message@ @en@ 805378135 @You cannot use the default branch view; it is just a sample.@ @pv@ 0 @db.message@ @en@ 805640629 @The Revision field can only be added to empty labels.@ @pv@ 0 @db.message@ @en@ 822155352 @Job fix status must be one of %values%.@ @pv@ 0 @db.message@ @en@ 1092687961 @%clientFile% - can't translate to local path -- no client!@ @pv@ 0 @db.message@ @en@ 1092687962 @Can't find %depot% in depot map!@ @pv@ 0 @db.message@ @en@ 1092687963 @Can't map %lbrFile% to archive!@ @pv@ 0 @db.message@ @en@ 1075910748 @RelateMap has empty maps!@ @pv@ 0 @db.message@ @en@ 807671901 @Invalid user (P4USER) or client (P4CLIENT) name.@ @pv@ 0 @db.message@ @en@ 807672379 @Command not allowed for a service user.@ @pv@ 0 @db.message@ @en@ 839260254 @Locked client '%client%' can only be used by owner '%user%'.@ @pv@ 0 @db.message@ @en@ 839260255 @Client '%client%' can only be used from host '%host%'.@ @pv@ 0 @db.message@ @en@ 805378144 @An empty string is not allowed as a file name.@ @pv@ 0 @db.message@ @en@ 805378145 @A revision specification (# or @@) cannot be used here.@ @pv@ 0 @db.message@ @en@ 805378146 @A revision range cannot be used here.@ @pv@ 0 @db.message@ @en@ 841226339 @%arg% - must create client '%client%' to access local files.@ @pv@ 0 @db.message@ @en@ 838998116 @%path% - must refer to client '%client%'.@ @pv@ 0 @db.message@ @en@ 822351973 @Invalid changelist/client/label/date '@@%arg%'.@ @pv@ 0 @db.message@ @en@ 822155366 @Unintelligible revision specification '%arg%'.@ @pv@ 0 @db.message@ @en@ 822155367 @Can't yet do relative operations on '%rev%'.@ @pv@ 0 @db.message@ @en@ 805378474 @Can't use a pending changelist number for this command.@ @pv@ 0 @db.message@ @en@ 822155700 @Too many revision specifications (max %max%).@ @pv@ 0 @db.message@ @en@ 822155719 @Too many automatic labels (label '%label%' may refer to itself).@ @pv@ 0 @db.message@ @en@ 807868855 @Client map too twisted for directory list.@ @pv@ 0 @db.message@ @en@ 554768488 @%reason%.@ @pv@ 0 @db.message@ @en@ 1092687977 @%path% - can't delete remote file!@ @pv@ 0 @db.message@ @en@ 1092687978 @%path% - can't checkin remote file!@ @pv@ 0 @db.message@ @en@ 824252523 @%text%@ @pv@ 0 @db.message@ @en@ 807737452 @Remote server is too old to support remote access. Install a new server.@ @pv@ 0 @db.message@ @en@ 824252525 @Remote depot '%depot%' database access failed.@ @pv@ 0 @db.message@ @en@ 824252526 @Remote depot '%depot%' archive access failed.@ @pv@ 0 @db.message@ @en@ 807606383 @Remote depot access is not supported between UNIX and NT prior to 99.2.@ @pv@ 0 @db.message@ @en@ 807475324 @Remote authorization server access failed.@ @pv@ 0 @db.message@ @en@ 1092688354 @Remote '%counter%' counter update failed.@ @pv@ 0 @db.message@ @en@ 1109465571 @Sequence error: local 'change' counter '%local%' vs remote '%remote%'!@ @pv@ 0 @db.message@ @en@ 1092688356 @Sequence error: next changelist '%change%' already exists!@ @pv@ 0 @db.message@ @en@ 1092819056 @%key% spec template unusable!@ @pv@ 0 @db.message@ @en@ 822155377 @Field %field% missing from form.@ @pv@ 0 @db.message@ @en@ 805378162 @Can't handle ^ (not) operator there.@ @pv@ 0 @db.message@ @en@ 838932596 @Fields '%field%' and '%field2%' have the same code.@ @pv@ 0 @db.message@ @en@ 838932893 @Fields '%field%' and '%field2%' have the same tag.@ @pv@ 0 @db.message@ @en@ 822155381 @Field '%field%' needs a preset value to be type '%opt%'.@ @pv@ 0 @db.message@ @en@ 822155382 @Default for '%field%' can't have ;'s in it.@ @pv@ 0 @db.message@ @en@ 304289911 @License count: %count% clients used of %max% licensed.@ @pv@ 0 @db.message@ @en@ 304289912 @License count: %count% users used of %max% licensed.@ @pv@ 0 @db.message@ @en@ 270735481 @Try deleting old clients with 'client -d'.@ @pv@ 0 @db.message@ @en@ 270735482 @Try deleting old users with 'user -d'.@ @pv@ 0 @db.message@ @en@ 805378171 @Too many client root alternatives -- only 2 allowed.@ @pv@ 0 @db.message@ @en@ 270735830 @ Additional users/clients may be obtained for evaluation purposes by visiting... http://www.perforce.com/eval @ @pv@ 0 @db.message@ @en@ 824646204 @File size exceeds dm.annotate.maxsize (%maxSize% bytes).@ @pv@ 0 @db.message@ @en@ 822155822 @%depot% is not an archive depot.@ @pv@ 0 @db.message@ @en@ 318773807 @Archiving %depotFile%%depotRev% to %archiveFile%.@ @pv@ 0 @db.message@ @en@ 318773808 @Restoring %depotFile%%depotRev% from %archiveFile%.@ @pv@ 0 @db.message@ @en@ 301996593 @Purged %depotFile%%depotRev%.@ @pv@ 0 @db.message@ @en@ 301996594 @Not archiving %depotFile%%depotRev%: head revision.@ @pv@ 0 @db.message@ @en@ 301996595 @Not archiving %depotFile%%depotRev%: lazy copy.@ @pv@ 0 @db.message@ @en@ 301996596 @Not archiving %depotFile%%depotRev%: content used elsewhere.@ @pv@ 0 @db.message@ @en@ 301996617 @Not archiving %depotFile%%depotRev%: trait 'archiveBucket' has been set.@ @pv@ 0 @db.message@ @en@ 318773813 @Not archiving %depotFile%%depotRev%: stored in delta format (+D).@ @pv@ 0 @db.message@ @en@ 536943158 @[%argc% - no|No] revisions can be archived.@ @pv@ 0 @db.message@ @en@ 536943159 @[%argc% - no|No] revisions can be restored.@ @pv@ 0 @db.message@ @en@ 536943160 @[%argc% - no|No] revisions can be purged.@ @pv@ 0 @db.message@ @en@ 318773448 @%change% created[ with %workCount% open file(s)][ fixing %jobCount% job(s)].@ @pv@ 0 @db.message@ @en@ 352327881 @%change% updated[, adding %workCount% file(s)][, removing %workCount2% file(s)][, adding %jobCount% fix(es)][, removing %jobCount2% fix(es)].@ @pv@ 0 @db.message@ @en@ 301996234 @%change% has %count% open file(s) associated with it and can't be deleted.@ @pv@ 0 @db.message@ @en@ 301996235 @%change% has %count% fixes associated with it and can't be deleted.@ @pv@ 0 @db.message@ @en@ 301996236 @%change% has %count% files associated with it and can't be deleted.@ @pv@ 0 @db.message@ @en@ 822286853 @%change% has shelved files associated with it and can't be deleted.@ @pv@ 0 @db.message@ @en@ 285219021 @%change% deleted.@ @pv@ 0 @db.message@ @en@ 838932948 @%change% can only be updated by user %user%.@ @pv@ 0 @db.message@ @en@ 838933053 @%change% can only be updated by user %user% with -u, or by admin user with -f.@ @pv@ 0 @db.message@ @en@ 838933054 @%change% can only be updated by user %user%, or by admin user with -f.@ @pv@ 0 @db.message@ @en@ 352327886 @%change% on %date% by %user%@@%client%%description%@ @pv@ 0 @db.message@ @en@ 352327887 @%change% on %date% by %user%@@%client% *pending*%description%@ @pv@ 0 @db.message@ @en@ 318773793 @%serverName%: %variableName% = %variableValue%@ @pv@ 0 @db.message@ @en@ 822221346 @No such configuration variable '%config%'.@ @pv@ 0 @db.message@ @en@ 822221347 @Configuration variable '%config%' did not have a value.@ @pv@ 0 @db.message@ @en@ 805444132 @Usage: { set [name#]var=value | unset [name#]var }@ @pv@ 0 @db.message@ @en@ 805575225 @Can't copy to target path with files already open.@ @pv@ 0 @db.message@ @en@ 301996240 @%counterName% = %counterValue%@ @pv@ 0 @db.message@ @en@ 285219025 @%dirName%@ @pv@ 0 @db.message@ @en@ 285219026 @Depot %depotName% saved.@ @pv@ 0 @db.message@ @en@ 285219027 @Depot %depotName% not changed.@ @pv@ 0 @db.message@ @en@ 285219028 @Depot %depotName% deleted.@ @pv@ 0 @db.message@ @en@ 822286756 @There is already a spec depot called '%depot%'.@ @pv@ 0 @db.message@ @en@ 822155706 @Map entry '%map%' must have only 1 wildcard which must be a trailing '/...' or '\...'.@ @pv@ 0 @db.message@ @en@ 822090235 @Depot type for '%depot%' must be 'stream'.@ @pv@ 0 @db.message@ @en@ 822286880 @Import path '%depotFile%' is not under an existing depot.@ @pv@ 0 @db.message@ @en@ 822286878 @Invalid parent field '%parent%'.@ @pv@ 0 @db.message@ @en@ 805378597 @Stream hierarchy in endless loop!@ @pv@ 0 @db.message@ @en@ 839064102 @No stream '%stream%' existed at change %change%@ @pv@ 0 @db.message@ @en@ 822155821 @Client '%client%' requires an application that can fully support streams.@ @pv@ 0 @db.message@ @en@ 838998591 @Missing stream '%name%' in stream hierarchy for '%stream%'.@ @pv@ 0 @db.message@ @en@ 822090304 @Stream '%stream%' is not the correct format of '//depotname/string' @ @pv@ 0 @db.message@ @en@ 822090306 @View '%view%' must be relative and not contain leading slashes @ @pv@ 0 @db.message@ @en@ 822090307 @Imported path '%view%' requires leading slashes in full depot path @ @pv@ 0 @db.message@ @en@ 822417988 @Stream '%stream%' has child streams; cannot delete until they are removed.@ @pv@ 0 @db.message@ @en@ 822417989 @Stream '%stream%' has active clients; cannot delete until they are removed.@ @pv@ 0 @db.message@ @en@ 872618567 @Stream '%stream%' (%type%) not compatible with Parent %parent% (%parentType%); use -u to force update.@ @pv@ 0 @db.message@ @en@ 855841352 @Stream '%stream%' (%oldType% -> %type%) not compatible with child streams; use -u to force update.@ @pv@ 0 @db.message@ @en@ 838867530 @Stream '%stream%' owner '%owner%' required for -u force update.@ @pv@ 0 @db.message@ @en@ 369105109 @%type% %depotName% %updateDate% %location% %map% '%description%'@ @pv@ 0 @db.message@ @en@ 385882326 @%type% %depotName% %updateDate% %location% %address% %map% '%description%'@ @pv@ 0 @db.message@ @en@ 352327895 @%change% by %user%@@%client% on %date%%description%@ @pv@ 0 @db.message@ @en@ 352327896 @%change% by %user%@@%client% on %date% *pending*%description%@ @pv@ 0 @db.message@ @en@ 318839001 @%depotFile%%depotRev% %action%@ @pv@ 0 @db.message@ @en@ 335616495 @%depotFile%%depotRev% moved from %depotFile2%%depotRev2%@ @pv@ 0 @db.message@ @en@ 335550682 @ ==== %depotFile%%depotRev% (%type%[/%type2%]) ==== @ @pv@ 0 @db.message@ @en@ 335550683 @==== %depotFile%%depotRev% - %localPath% ====[ (%type%)]@ @pv@ 0 @db.message@ @en@ 301996252 @==== %depotFile%%depotRev% - ===@ @pv@ 0 @db.message@ @en@ 301996253 @==== - %depotFile%%depotRev% ====@ @pv@ 0 @db.message@ @en@ 301996455 @==== < none > - %depotFile%%depotRev% ====@ @pv@ 0 @db.message@ @en@ 369105118 @==== %depotFile%%depotRev% (%type%) - %depotFile2%%depotRev2% (%type2%) ==== content@ @pv@ 0 @db.message@ @en@ 369105119 @==== %depotFile%%depotRev% (%type%) - %depotFile2%%depotRev2% (%type2%) ==== types@ @pv@ 0 @db.message@ @en@ 369105120 @==== %depotFile%%depotRev% (%type%) - %depotFile2%%depotRev2% (%type2%) ==== identical@ @pv@ 0 @db.message@ @en@ 335550689 @--- %depotFile% %depotDate% +++ %depotFile2% %depotDate2%@ @pv@ 0 @db.message@ @en@ 335550935 @Binary files %depotFile%%depotRev% and %depotFile2%%depotRev2% differ@ @pv@ 0 @db.message@ @en@ 301996258 @%domainType% %domainName% saved.@ @pv@ 0 @db.message@ @en@ 301996259 @%domainType% %domainName% not changed.@ @pv@ 0 @db.message@ @en@ 301996260 @%domainType% %domainName% deleted.@ @pv@ 0 @db.message@ @en@ 352327909 @%domainType% %domainName% %updateDate% root %domainMount% '%description%'@ @pv@ 0 @db.message@ @en@ 335550694 @%domainType% %domainName% %updateDate% '%description%'@ @pv@ 0 @db.message@ @en@ 335550926 @%file%%rev% duplicated from %file2%%rev2%@ @pv@ 0 @db.message@ @en@ 301996495 @%file%%rev% already exists@ @pv@ 0 @db.message@ @en@ 335550928 @%file%%rev% is opened for %action% on client %client%@ @pv@ 0 @db.message@ @en@ 285219047 @%depotFile%@ @pv@ 0 @db.message@ @en@ 335616232 @%depotRev% %change% %action% on %date%@ @pv@ 0 @db.message@ @en@ 402725097 @%depotRev% %change% %action% on %date% by %user%@@%client% (%type%)%description%@ @pv@ 0 @db.message@ @en@ 318904554 @%how% %fromFile%%fromRev%@ @pv@ 0 @db.message@ @en@ 352327915 @%depotFile%%depotRev% - %action% %change% (%type%)@ @pv@ 0 @db.message@ @en@ 335550910 @%path% %fileCount% files %fileSize% bytes [%blockCount% blocks]@ @pv@ 0 @db.message@ @en@ 335550918 @%depotFile%%depotRev% %fileSize% bytes [%blockCount% blocks]@ @pv@ 0 @db.message@ @en@ 318773484 @%job% fixed by %change% (%status%).@ @pv@ 0 @db.message@ @en@ 301996270 @Deleted fix %job% by %change%.@ @pv@ 0 @db.message@ @en@ 369105135 @%job% fixed by %change% on %date% by %user%@@%client% (%status%)@ @pv@ 0 @db.message@ @en@ 335550995 @%depotFile%#%depotRev%%separator%%linecontent%@ @pv@ 0 @db.message@ @en@ 301996564 @%depotFile%#%depotRev%@ @pv@ 0 @db.message@ @en@ 369105429 @%depotFile%#%depotRev%%separator1%%linenumber%%separator2%%linecontent%@ @pv@ 0 @db.message@ @en@ 603986454 @%depotFile%#%depotRev% - line %linenumber%: maximum line length of %maxlinelength% exceeded@ @pv@ 0 @db.message@ @en@ 822155799 @Grep revision limit exceeded (over %maxRevs%).@ @pv@ 0 @db.message@ @en@ 268442136 @--@ @pv@ 0 @db.message@ @en@ 285219057 @Group %group% created.@ @pv@ 0 @db.message@ @en@ 285219058 @Group %group% not created.@ @pv@ 0 @db.message@ @en@ 285219059 @Group %group% deleted.@ @pv@ 0 @db.message@ @en@ 285219060 @Group %group% not updated.@ @pv@ 0 @db.message@ @en@ 285219061 @Group %group% updated.@ @pv@ 0 @db.message@ @en@ 838867416 @User '%user%' is not an owner of group '%group%'.@ @pv@ 0 @db.message@ @en@ 285219062 @%group%@ @pv@ 0 @db.message@ @en@ 352328154 @%group% %maxresults% %maxscanrows% %maxtimeout% %timeout%@ @pv@ 0 @db.message@ @en@ 318773495 @%depotFile%%haveRev% - %lp%@ @pv@ 0 @db.message@ @en@ 301996282 @%depotFile% - can't %action% (already opened on this client)@ @pv@ 0 @db.message@ @en@ 301996283 @%depotFile% - can only %action% into file in a local depot@ @pv@ 0 @db.message@ @en@ 301996284 @%depotFile% - can't %action% exclusive file already opened@ @pv@ 0 @db.message@ @en@ 352327933 @%depotFile% - can't %action% from %fromFile%%fromRev% without -d or %flag% flag@ @pv@ 0 @db.message@ @en@ 335550718 @%depotFile% - can't %action% from %fromFile%%fromRev% without -i flag@ @pv@ 0 @db.message@ @en@ 318773503 @%depotFile% - can't %action% (already opened for %badAction%)@ @pv@ 0 @db.message@ @en@ 301996288 @%depotFile% - is already opened by client %client%@ @pv@ 0 @db.message@ @en@ 301996289 @%depotFile% - is already opened by user %user%@ @pv@ 0 @db.message@ @en@ 301996290 @%depotFile% - can't %action% existing file@ @pv@ 0 @db.message@ @en@ 301996291 @%depotFile% - can't %action% deleted file@ @pv@ 0 @db.message@ @en@ 285219076 @%toFile% - must sync before integrating.@ @pv@ 0 @db.message@ @en@ 402659752 @%depotFile%%workRev% - %action% from %fromFile%%fromRev%[ using base %baseFile%][%baseRev%][ (moved from %movedFrom%)]@ @pv@ 0 @db.message@ @en@ 352327942 @%depotFile%%workRev% - %action%/sync from %fromFile%%fromRev%@ @pv@ 0 @db.message@ @en@ 352328107 @%depotFile%%workRev% - sync/%action% from %fromFile%%fromRev%[ using base %baseFile%][%baseRev%][ (moved from %movedFrom%)]@ @pv@ 0 @db.message@ @en@ 318773512 @%depotFile%%workRev% - flag %flag% not handled!@ @pv@ 0 @db.message@ @en@ 301996481 @%depotFile% - can't %action% file branched with integrate -v@ @pv@ 0 @db.message@ @en@ 301996493 @%depotFile% - file type of %fromFile% incompatible@ @pv@ 0 @db.message@ @en@ 301996583 @%depotFile% - not in client view (moved from %movedFrom%)@ @pv@ 0 @db.message@ @en@ 301996584 @%depotFile% - no permission (moved from %movedFrom%)@ @pv@ 0 @db.message@ @en@ 301996588 @%depotFile% - not in branch view (moved from %movedFrom%)@ @pv@ 0 @db.message@ @en@ 352327945 @%toFile%%toRev% - %how% %fromFile%%fromRev%@ @pv@ 0 @db.message@ @en@ 285219082 @Job %job% saved.@ @pv@ 0 @db.message@ @en@ 285219083 @Job %job% not changed.@ @pv@ 0 @db.message@ @en@ 285219084 @Job %job% deleted.@ @pv@ 0 @db.message@ @en@ 352327949 @%job%[ on %date%][ by %user%][ *%status%*][%description%]@ @pv@ 0 @db.message@ @en@ 301996497 @%job% has %count% fixes associated with it and can't be deleted.@ @pv@ 0 @db.message@ @en@ 301996304 @%depotFile%%haveRev% - added@ @pv@ 0 @db.message@ @en@ 301996305 @%depotFile%%haveRev% - deleted@ @pv@ 0 @db.message@ @en@ 301996306 @%depotFile%%haveRev% - replaced@ @pv@ 0 @db.message@ @en@ 301996307 @%depotFile%%haveRev% - updated@ @pv@ 0 @db.message@ @en@ 268442050 @License file saved.@ @pv@ 0 @db.message@ @en@ 268442051 @License file not changed.@ @pv@ 0 @db.message@ @en@ 285219092 @%depotFile% - locking@ @pv@ 0 @db.message@ @en@ 285219093 @%depotFile% - already locked@ @pv@ 0 @db.message@ @en@ 318773526 @%depotFile% - already locked by %user%@@%client%@ @pv@ 0 @db.message@ @en@ 285219095 @%depotFile% - no permission to lock file@ @pv@ 0 @db.message@ @en@ 285219341 @%depotFile% - cannot submit unicode type file using non-unicode server@ @pv@ 0 @db.message@ @en@ 285219342 @%depotFile% - utf16 files can not be submitted by pre-2007.2 clients@ @pv@ 0 @db.message@ @en@ 285219096 @%depotFile% - unlocking@ @pv@ 0 @db.message@ @en@ 285219097 @%depotFile% - already unlocked@ @pv@ 0 @db.message@ @en@ 318773530 @%depotFile% - locked by %user%@@%client%@ @pv@ 0 @db.message@ @en@ 318773531 @%sequence% %key% %attribute%@ @pv@ 0 @db.message@ @en@ 335550951 @%toFile%%toRev% - moved from %fromFile%%fromRev%@ @pv@ 0 @db.message@ @en@ 301996520 @%depotFile% - can't move (already opened for %badAction%)@ @pv@ 0 @db.message@ @en@ 285219305 @%depotFile% - can't move to an existing file@ @pv@ 0 @db.message@ @en@ 1075911146 @Mismatched move on client!@ @pv@ 0 @db.message@ @en@ 318773739 @%depotFile% - needs %direction%file %movedFile%@ @pv@ 0 @db.message@ @en@ 285219310 @%depotFile% - can't move to a spec or remote depot@ @pv@ 0 @db.message@ @en@ 285219344 @%depotFile% - not synced, can't force move@ @pv@ 0 @db.message@ @en@ 285219345 @%depotFile% - is unresolved, can't force move@ @pv@ 0 @db.message@ @en@ 285219346 @%clientFile% - is synced; use -f to force move@ @pv@ 0 @db.message@ @en@ 301996316 @%depotFile% - can't %action% (already opened on this client)@ @pv@ 0 @db.message@ @en@ 301996317 @%depotFile% - can only %action% file in a local depot@ @pv@ 0 @db.message@ @en@ 301996318 @%depotFile% - can't %action% exclusive file already opened@ @pv@ 0 @db.message@ @en@ 318773535 @%depotFile% - can't %action% (already opened for %badAction%)@ @pv@ 0 @db.message@ @en@ 301996320 @%depotFile% - is already opened by client %client%@ @pv@ 0 @db.message@ @en@ 301996321 @%depotFile% - is already opened by user %user%@ @pv@ 0 @db.message@ @en@ 301996322 @%depotFile% - can't change from %change% - use 'reopen'@ @pv@ 0 @db.message@ @en@ 301996323 @%depotFile% - can't change from %type% - use 'reopen'@ @pv@ 0 @db.message@ @en@ 318773540 @%depotFile%%workRev% - reopened for %action%@ @pv@ 0 @db.message@ @en@ 318773541 @%depotFile%%workRev% - currently opened for %action%@ @pv@ 0 @db.message@ @en@ 301996326 @%depotFile% - can't %action% existing file@ @pv@ 0 @db.message@ @en@ 301996327 @%depotFile% - can't %action% deleted file@ @pv@ 0 @db.message@ @en@ 318773544 @%depotFile%%workRev% - opened for %action%@ @pv@ 0 @db.message@ @en@ 302061865 @%depotFile% - must sync/resolve %workRev% before submitting@ @pv@ 0 @db.message@ @en@ 318839082 @%depotFile% - locked by %user%@@%client%@ @pv@ 0 @db.message@ @en@ 318839083 @%depotFile% - also opened by %user%@@%client%@ @pv@ 0 @db.message@ @en@ 302061868 @%depotFile% - warning: %action% of existing file@ @pv@ 0 @db.message@ @en@ 302061869 @%depotFile% - warning: %action% of deleted file@ @pv@ 0 @db.message@ @en@ 302062061 @%depotFile% - warning: %action% of moved file@ @pv@ 0 @db.message@ @en@ 285284905 @%depotFile% - warning: cannot submit from non-stream client@ @pv@ 0 @db.message@ @en@ 302062122 @%depotFile% - warning: cannot submit from stream %stream% client@ @pv@ 0 @db.message@ @en@ 302062138 @%depotFile% - warning: file not mapped in stream %stream% client@ @pv@ 0 @db.message@ @en@ 352327982 @%depotFile%%workRev% - %action% %change% (%type%)@ @pv@ 0 @db.message@ @en@ 385882415 @%depotFile%%workRev% - %action% %change% (%type%) by %user%@@%client%@ @pv@ 0 @db.message@ @en@ 352327984 @%depotFile%%workRev% - %action% %change% (%type%) *locked*@ @pv@ 0 @db.message@ @en@ 385882417 @%depotFile%%workRev% - %action% %change% (%type%) by %user%@@%client% *locked*@ @pv@ 0 @db.message@ @en@ 268441906 @Protections saved.@ @pv@ 0 @db.message@ @en@ 268441907 @Protections not changed.@ @pv@ 0 @db.message@ @en@ 385882552 @%perm% %isgroup% %user% %ipaddr% %mapFlag%%depotFile%@ @pv@ 0 @db.message@ @en@ 285219268 @%perm%@ @pv@ 0 @db.message@ @en@ 807606728 @Protections table is empty.@ @pv@ 0 @db.message@ @en@ 807606741 @Can't delete last valid 'super' entry from protections table.@ @pv@ 0 @db.message@ @en@ 335550772 @%depotFile%%depotRev% - copy from %lbrFile% %lbrRev%@ @pv@ 0 @db.message@ @en@ 352327989 @Deleted [%onHave% client ][%onLabel% label ][%onInteg% integration ][%onWorking% opened ][%onRev% revision ][and added %synInteg% integration ]record(s).@ @pv@ 0 @db.message@ @en@ 352327990 @Would delete [%onHave% client ][%onLabel% label ][%onInteg% integration ][%onWorking% opened ][%onRev% revision ][and add %synInteg% integration ]record(s).@ @pv@ 0 @db.message@ @en@ 268441911 @No records to delete.@ @pv@ 0 @db.message@ @en@ 301996344 @%depotFile%%depotRev% - purged@ @pv@ 0 @db.message@ @en@ 301996345 @%depotFile%%haveRev% - has pending integrations, not reverted@ @pv@ 0 @db.message@ @en@ 318773562 @%depotFile%%haveRev% - was %action%, abandoned@ @pv@ 0 @db.message@ @en@ 318773563 @%depotFile%%haveRev% - was %action%, cleared@ @pv@ 0 @db.message@ @en@ 318773564 @%depotFile%%haveRev% - was %action%, deleted@ @pv@ 0 @db.message@ @en@ 318773565 @%depotFile%%haveRev% - was %action%, reverted@ @pv@ 0 @db.message@ @en@ 318773566 @%depotFile%%haveRev% - was %action%, unlocked and abandoned@ @pv@ 0 @db.message@ @en@ 318773567 @%depotFile%%haveRev% - was %action%, unlocked and cleared@ @pv@ 0 @db.message@ @en@ 318773568 @%depotFile%%haveRev% - was %action%, unlocked and deleted@ @pv@ 0 @db.message@ @en@ 318773569 @%depotFile%%haveRev% - was %action%, unlocked and reverted@ @pv@ 0 @db.message@ @en@ 318773691 @%depotFile%%haveRev% - belongs to user %user%, not reverted@ @pv@ 0 @db.message@ @en@ 301996518 @%depotFile%%haveRev% - has been moved, not reverted@ @pv@ 0 @db.message@ @en@ 352328002 @%depotFile%%workRev% - reopened[; user %user%][; type %type%][; %change%]@ @pv@ 0 @db.message@ @en@ 352328003 @%depotFile%%workRev% - nothing changed[; user %user%][; type %type%][; %change%]@ @pv@ 0 @db.message@ @en@ 285219140 @%localPath% - has been deleted - revert and sync.@ @pv@ 0 @db.message@ @en@ 318773573 @%localPath% - vs %fromFile%%fromRev%@ @pv@ 0 @db.message@ @en@ 352328006 @%localPath% - %baseType%/%headType% merge %fromFile%%fromRev%@ @pv@ 0 @db.message@ @en@ 318773575 @%localPath% - merging %fromFile%%fromRev%@ @pv@ 0 @db.message@ @en@ 318773673 @%localPath% - merging %fromFile%%fromRev% using base %baseFile%%baseRev%@ @pv@ 0 @db.message@ @en@ 335550792 @%localPath% - %how% %fromFile%%fromRev%@ @pv@ 0 @db.message@ @en@ 335550892 @%localPath% - %how% %fromFile%%fromRev% base %baseFile%%baseRev%@ @pv@ 0 @db.message@ @en@ 335550923 @%depotFile%%depotRev% - %oldType% now %newType%@ @pv@ 0 @db.message@ @en@ 335550793 @%change% %user% <%email%> (%fullName%)@ @pv@ 0 @db.message@ @en@ 318773578 @%user% <%email%> (%fullname%)@ @pv@ 0 @db.message@ @en@ 285219230 @Spec %type% saved.@ @pv@ 0 @db.message@ @en@ 285219231 @Spec %type% not changed.@ @pv@ 0 @db.message@ @en@ 285219232 @Spec %type% deleted.@ @pv@ 0 @db.message@ @en@ 822221217 @Spec %type% not defined.@ @pv@ 0 @db.message@ @en@ 822155776 @%depotFile% - already shelved, use -f to update.@ @pv@ 0 @db.message@ @en@ 285219334 @%depotFile% - shelved file locked, try again later.@ @pv@ 0 @db.message@ @en@ 285219335 @%depotFile% - shelved file unlocked, try again later.@ @pv@ 0 @db.message@ @en@ 822155786 @%depotFile% - can't overwrite a shelved moved file, use -r to replace.@ @pv@ 0 @db.message@ @en@ 822155787 @Shelve file limit exceeded (over %maxFiles%).@ @pv@ 0 @db.message@ @en@ 285219357 @%depotFile% - no permission to shelve file@ @pv@ 0 @db.message@ @en@ 822155760 @'%tag%' unknown or wrong number of fields for path-type.@ @pv@ 0 @db.message@ @en@ 838867441 @Stream '%stream%' is owned by '%owner%'.@ @pv@ 0 @db.message@ @en@ 352328178 @Stream %stream% %type% %parent% %title%[ %status%]@ @pv@ 0 @db.message@ @en@ 822090227 @Stream '%stream%' must begin with '//'.@ @pv@ 0 @db.message@ @en@ 822090228 @Stream '%stream%' is ownersubmit and cannot be source of new stream .@ @pv@ 0 @db.message@ @en@ 838867445 @Streams cannot be nested. '%stream%' contains existing stream '%nested%'.@ @pv@ 0 @db.message@ @en@ 822090230 @Stream '%stream%' contains embedded double slashes (//).@ @pv@ 0 @db.message@ @en@ 822090231 @Stream '%stream%' must be below depot level.@ @pv@ 0 @db.message@ @en@ 822090232 @Stream '%stream%' must reside in first folder below depot level.@ @pv@ 0 @db.message@ @en@ 822090233 @Stream '%stream%' cannot end with slash.@ @pv@ 0 @db.message@ @en@ 1075911162 @Stream and domains table out of sync!@ @pv@ 0 @db.message@ @en@ 838932994 @%loc% wildcards (*, ...) not allowed in path: '%path%'.@ @pv@ 0 @db.message@ @en@ 822155807 @Embedded wildcards (*, ...) not allowed in '%path%'.@ @pv@ 0 @db.message@ @en@ 822155779 @Positional wildcards (%%%%x) not allowed in path: '%path%'.@ @pv@ 0 @db.message@ @en@ 822090310 @Owner field of Stream '%stream%' required.@ @pv@ 0 @db.message@ @en@ 301996363 @%depotFile% - opened at head rev %workRev%@ @pv@ 0 @db.message@ @en@ 301996364 @%depotFile% - %action% of added file; must revert@ @pv@ 0 @db.message@ @en@ 301996365 @%depotFile% - %action% of deleted file; must revert@ @pv@ 0 @db.message@ @en@ 301996571 @%depotFile% - %action% of deleted file; must sync & add -d or revert@ @pv@ 0 @db.message@ @en@ 285219150 @%depotFile% - must resolve before submitting@ @pv@ 0 @db.message@ @en@ 318773583 @%action% %depotFile%%depotRev%@ @pv@ 0 @db.message@ @en@ 301996368 @%depotFile%%depotRev% - refreshing@ @pv@ 0 @db.message@ @en@ 301996476 @%depotFile%%depotRev% - unchanged, reverted@ @pv@ 0 @db.message@ @en@ 301996477 @%depotFile%%depotRev% - unchanged, moved to default changelist@ @pv@ 0 @db.message@ @en@ 318773585 @%toFile% - must resolve %fromFile%%fromRev%@ @pv@ 0 @db.message@ @en@ 301996370 @%fromFile% - must resolve %fromRev%@ @pv@ 0 @db.message@ @en@ 301996371 @Use 'p4 submit -c %change%' to submit file(s) in pending %newChange%.@ @pv@ 0 @db.message@ @en@ 318773588 @%depotFile%%depotRev% - added as %localPath%@ @pv@ 0 @db.message@ @en@ 318773589 @%depotFile%%haveRev% - deleted as %localPath%@ @pv@ 0 @db.message@ @en@ 318773590 @%depotFile%%depotRev% - replacing %localPath%@ @pv@ 0 @db.message@ @en@ 318773591 @%depotFile%%workRev% - is opened for %action% and can't be deleted@ @pv@ 0 @db.message@ @en@ 318773592 @%depotFile%%workRev% - is opened for %action% and can't be replaced@ @pv@ 0 @db.message@ @en@ 318773593 @%depotFile%%depotRev% - updating %localPath%@ @pv@ 0 @db.message@ @en@ 318773594 @%depotFile%%depotRev% - refreshing %localPath%@ @pv@ 0 @db.message@ @en@ 301996379 @%depotFile%%workRev% - is opened and not being changed@ @pv@ 0 @db.message@ @en@ 318773596 @%depotFile%%workRev% - is opened for %action% - not changed@ @pv@ 0 @db.message@ @en@ 301996381 @%depotFile%%workRev% - is opened at a later revision - not changed@ @pv@ 0 @db.message@ @en@ 301996382 @%depotFile%%haveRev% - is up-to-date@ @pv@ 0 @db.message@ @en@ 302061919 @%depotFile% - must resolve %revRange% before submitting@ @pv@ 0 @db.message@ @en@ 285219273 @%depotFile% - can't sync -p a file that's opened@ @pv@ 0 @db.message@ @en@ 285219274 @%depotFile% - can't sync -p a file that's synced@ @pv@ 0 @db.message@ @en@ 301996524 @%depotFile% - can't sync moved file, %fromFile% is missing from the rev table!@ @pv@ 0 @db.message@ @en@ 318773677 @%depotFile%%depotRev% - %name% cleared@ @pv@ 0 @db.message@ @en@ 318773678 @%depotFile%%depotRev% - %name% not set@ @pv@ 0 @db.message@ @en@ 318773679 @%depotFile%%depotRev% - %name% set@ @pv@ 0 @db.message@ @en@ 268441952 @Triggers saved.@ @pv@ 0 @db.message@ @en@ 268441953 @Triggers not changed.@ @pv@ 0 @db.message@ @en@ 285219170 @%type% saved.@ @pv@ 0 @db.message@ @en@ 285219171 @%type% not changed.@ @pv@ 0 @db.message@ @en@ 301996542 @%depotFile% - can't unshelve (already opened for %badAction%)@ @pv@ 0 @db.message@ @en@ 301996552 @Can't unshelve %depotFile% to open for %badAdd%: file already exists.@ @pv@ 0 @db.message@ @en@ 301996553 @Can't unshelve %depotFile% to open for %badEdit%: file does not exist or has been deleted.@ @pv@ 0 @db.message@ @en@ 318773759 @%depotFile%%depotRev% - unshelved, opened for %action%@ @pv@ 0 @db.message@ @en@ 805378561 @File(s) in this shelve are locked - try again later!@ @pv@ 0 @db.message@ @en@ 285219172 @User %user% saved.@ @pv@ 0 @db.message@ @en@ 285219173 @User %user% not changed.@ @pv@ 0 @db.message@ @en@ 822221158 @User %user% doesn't exist.@ @pv@ 0 @db.message@ @en@ 301996391 @User %user% has file(s) open on %value% client(s) and can't be deleted.@ @pv@ 0 @db.message@ @en@ 285219176 @User %user% deleted.@ @pv@ 0 @db.message@ @en@ 335550825 @%user% <%email%> (%fullName%) accessed %accessDate%@ @pv@ 0 @db.message@ @en@ 385882667 @%user% <%email%> (%fullName%) accessed %accessDate% type %type% ticket expires %endDate% password last changed %passDate%@ @pv@ 0 @db.message@ @en@ 385882474 @%depotFile%%depotRev% - %action% %change% (%type%) %digest%[ %status%]@ @pv@ 0 @db.message@ @en@ 335550828 @%mapFlag%%depotFile% %clientFile% %localPath%@ @pv@ 0 @db.message@ @en@ 554768749 @[%argc% - no|No] such changelist.@ @pv@ 0 @db.message@ @en@ 554768892 @[%argc% - no|No] such stream.@ @pv@ 0 @db.message@ @en@ 554768750 @[%argc% - no|No] such user(s).@ @pv@ 0 @db.message@ @en@ 554768751 @[%argc% - file(s)|File(s)] not in client view.@ @pv@ 0 @db.message@ @en@ 571546077 @%!%[%argc% - file(s)|File(s)] not in client view.@ @pv@ 0 @db.message@ @en@ 554768862 @[%argc% - no|No] source file(s) in branch view.@ @pv@ 0 @db.message@ @en@ 571546079 @%!%[%argc% - no|No] target file(s) in branch view.@ @pv@ 0 @db.message@ @en@ 571545968 @%!%[%argc% - no|No] target file(s) in both client and branch view.@ @pv@ 0 @db.message@ @en@ 554768753 @[%argc% - no|No] permission for operation on file(s).@ @pv@ 0 @db.message@ @en@ 571546080 @%!%[%argc% - no|No] permission for operation on file(s).@ @pv@ 0 @db.message@ @en@ 554768754 @[%argc% - protected|Protected] namespace - access denied.@ @pv@ 0 @db.message@ @en@ 571546081 @%!%[%argc% - protected|Protected] namespace - access denied.@ @pv@ 0 @db.message@ @en@ 554768755 @[%argc% - all|All] revision(s) already integrated in pending changelist.@ @pv@ 0 @db.message@ @en@ 554768756 @[%argc% - all|All] revision(s) already integrated.@ @pv@ 0 @db.message@ @en@ 554768757 @[%argc% - no|No] differing files.@ @pv@ 0 @db.message@ @en@ 554768911 @[%argc% - no|No] file(s) to diff.@ @pv@ 0 @db.message@ @en@ 554768758 @[%argc% - file(s)|File(s)] already have digests.@ @pv@ 0 @db.message@ @en@ 554768759 @[%argc% - no|No] such file(s).@ @pv@ 0 @db.message@ @en@ 554768760 @[%argc% - file(s)|File(s)] not on client.@ @pv@ 0 @db.message@ @en@ 554768761 @[%argc% - no|No] file(s) integrated.@ @pv@ 0 @db.message@ @en@ 554768762 @[%argc% - file(s)|File(s)] not in label.@ @pv@ 0 @db.message@ @en@ 554768763 @[%argc% - label|Label] in sync.@ @pv@ 0 @db.message@ @en@ 554768764 @[%argc% - file(s)|File(s)] not opened anywhere.@ @pv@ 0 @db.message@ @en@ 554768765 @[%argc% - file(s)|File(s)] not opened in that changelist.@ @pv@ 0 @db.message@ @en@ 554768766 @[%argc% - file(s)|File(s)] not opened on this client.@ @pv@ 0 @db.message@ @en@ 554768767 @[%argc% - file(s)|File(s)] not opened for edit.@ @pv@ 0 @db.message@ @en@ 554768768 @[%argc% - file(s)|File(s)] not opened in default changelist.@ @pv@ 0 @db.message@ @en@ 554768769 @[%argc% - no|No] file(s) resolved.@ @pv@ 0 @db.message@ @en@ 554768771 @[%argc% - no|No] file(s) to resolve.@ @pv@ 0 @db.message@ @en@ 554768772 @[%argc% - file(s)|File(s)] up-to-date.@ @pv@ 0 @db.message@ @en@ 554768900 @[%argc% - no|No] file(s) to unshelve.@ @pv@ 0 @db.message@ @en@ 554768773 @[%argc% - no|No] revision(s) above those at that changelist number.@ @pv@ 0 @db.message@ @en@ 554768774 @[%argc% - no|No] revision(s) after that date.@ @pv@ 0 @db.message@ @en@ 554768775 @[%argc% - no|No] revision(s) above those on client.@ @pv@ 0 @db.message@ @en@ 554768776 @[%argc% - no|No] revision(s) above those in label.@ @pv@ 0 @db.message@ @en@ 554768777 @[%argc% - no|No] revision(s) above that revision.@ @pv@ 0 @db.message@ @en@ 554768778 @[%argc% - no|No] file(s) at that changelist number.@ @pv@ 0 @db.message@ @en@ 554768779 @[%argc% - no|No] file(s) as of that date.@ @pv@ 0 @db.message@ @en@ 554768780 @[%argc% - file(s)|File(s)] not on client.@ @pv@ 0 @db.message@ @en@ 554768781 @[%argc% - file(s)|File(s)] not in label.@ @pv@ 0 @db.message@ @en@ 554768782 @[%argc% - no|No] file(s) at that revision.@ @pv@ 0 @db.message@ @en@ 554768783 @[%argc% - no|No] file(s) with that action.@ @pv@ 0 @db.message@ @en@ 554768924 @[%argc% - no|No] file(s) of type text.@ @pv@ 0 @db.message@ @en@ 554768784 @[%argc% - no|No] revision(s) below those at that changelist number.@ @pv@ 0 @db.message@ @en@ 554768785 @[%argc% - no|No] revision(s) before that date.@ @pv@ 0 @db.message@ @en@ 554768786 @[%argc% - no|No] revision(s) below those on client.@ @pv@ 0 @db.message@ @en@ 554768787 @[%argc% - no|No] revision(s) below those in label.@ @pv@ 0 @db.message@ @en@ 554768788 @[%argc% - no|No] revision(s) below that revision.@ @pv@ 0 @db.message@ @en@ 302061973 @%depotFile% - warning: %action% of purged file@ @pv@ 0 @db.message@ @en@ 419436950 @%id% [%prog% ][%host%][%runstate%|T] %user% [%client% ]%elapsed% %function% %args%@ @pv@ 0 @db.message@ @en@ 285219223 @** process '%id%' record cleared **@ @pv@ 0 @db.message@ @en@ 285219224 @** process '%id%' marked for termination **@ @pv@ 0 @db.message@ @en@ 285219225 @** process '%id%' can't terminate, runtime < 10 seconds **@ @pv@ 0 @db.message@ @en@ 285219282 @%depotFile% - created@ @pv@ 0 @db.message@ @en@ 839061543 @Path '%path%' is not under client's root '%root%'.@ @pv@ 0 @db.message@ @en@ 839061544 @Path '%path%' is not under client '%client%'.@ @pv@ 0 @db.message@ @en@ 807800894 @Command terminated because client closed connection.@ @pv@ 0 @db.message@ @en@ 824381472 @Request too large (over %maxResults%); see 'p4 help maxresults'.@ @pv@ 0 @db.message@ @en@ 824381501 @Too many rows scanned (over %maxScanRows%); see 'p4 help maxscanrows'.@ @pv@ 0 @db.message@ @en@ 824383941 @Operation took too long (over %maxLockTime% seconds); see 'p4 help maxlocktime'.@ @pv@ 0 @db.message@ @en@ 287513051 @Write: %name%@ @pv@ 0 @db.message@ @en@ 287513052 @Read : %name%@ @pv@ 0 @db.message@ @en@ 822155280 @Invalid MaxScanRow number '%value%'.@ @pv@ 0 @db.message@ @en@ 822351941 @Error in %domain% specification.@ @pv@ 0 @db.message@ @en@ 805378127 @A job name field with code 101 must be present.@ @pv@ 0 @db.message@ @en@ 822155379 @Code 0 not allowed on field '%field%'.@ @pv@ 0 @db.message@ @en@ 301996269 @%job% fixed by %change%.@ @pv@ 0 @db.message@ @en@ 352327920 @%job% fixed by %change% on %date% by %user%@@%client%@ @pv@ 0 @db.message@ @en@ 285219064 @%domainType% unknown.@ @pv@ 0 @db.message@ @en@ 301996281 @%domainType% root: %root%@ @pv@ 0 @db.message@ @en@ 268441870 @Spec %type% saved.@ @pv@ 0 @db.message@ @en@ 268441871 @Spec %type% not changed.@ @pv@ 0 @db.message@ @en@ 554768770 @[%argc% - no|No] file(s) to integrate.@ @pv@ 0 @db.message@ @en@ 352327941 @%depotFile%%workRev% - %action% from %fromFile%%fromRev%@ @pv@ 0 @db.message@ @en@ 352327943 @%depotFile%%workRev% - sync/%action% from %fromFile%%fromRev%@ @pv@ 0 @db.message@ @en@ 822159361 @No help for %command%.@ @pv@ 0 @db.message@ @en@ 302000139 @ Perforce -- the Fast Software Configuration Management System. p4 is Perforce's client tool for the command line. Try: p4 help simple list most common commands p4 help commands list all commands p4 help command help on a specific command p4 help charset help on character set translation p4 help configurables list server configuration variables p4 help environment list environment and registry variables p4 help filetypes list supported file types p4 help jobview help on jobview syntax p4 help revisions help on specifying file revisions p4 help usage generic command line arguments p4 help views help on view syntax The full user manual is available at http://www.perforce.com/manual. Server %release_id%/%patch_id%. @ @pv@ 0 @db.message@ @en@ 268445708 @ Perforce client usage: p4 [options] command [arg ...] p4 -V options: -c client -C charset -d dir -H host -G -L language -p port -P pass -s -Q charset -u user -x file -z tag The -c flag specifies the client name, overriding the value of $P4CLIENT in the environment and the default (the hostname). The -C flag specifies the client's character set, overriding the value of $P4CHARSET in the environment. See 'p4 help charset' for more information. The -d flag specifies the current directory, overriding the value of $PWD in the environment and the default (the current directory). The -G flag formats all output (and batch input for form commands with -i) as marshalled Python dictionary objects. The -H flag specifies the host name, overriding the value of $P4HOST in the environment and the default (the hostname). The -L flag specifies the language for text messages from the server, overriding the value of $P4LANGUAGE in the environment. Setting this option only works if the administrator has loaded support for non-English messages into the server database. The -p flag specifies the server's listen address, overriding the value of $P4PORT in the environment and the default (perforce:1666). The -P flag specifies the password, overriding the value of $P4PASSWD in the environment. The -Q flag specifies the client's command character set, overriding the value of $P4COMMANDCHARSET in the environment. See 'p4 help charset' for more information. The -s flag causes the p4 command line client program to prefix each line of output with a tag (error, warning, info, text, exit) to make it easier to use for scripting. The -u flag specifies the user name, overriding the value of $P4USER, $USER, and $USERNAME in the environment. The -x flag instructs p4 to read arguments, one per line, from the specified file. If you specify '-', standard input is read. The -V flag displays the version of the p4 client command and exits. The -z tag option returns output of reporting commands in the format returned by 'p4 fstat'. @ @pv@ 0 @db.message@ @en@ 268445709 @ Most common Perforce client commands: client Create or edit a client specification and its view sync Synchronize the client with its view of the depot add Open a new file to add it to the depot edit Open an existing file for edit delete Open an existing file to delete it from the depot resolve Merge open files with other revisions or files revert Discard changes from an opened file submit Submit open files to the depot @ @pv@ 0 @db.message@ @en@ 268445710 @ Perforce client commands: add Open a new file to add it to the depot admin Perform administrative operations on the server annotate Print file lines along with their revisions archive Archive obsolete revisions to archive depots. branch Create or edit a branch specification branches Display list of branches browse Browse for a list of zeroconf registered Perforce servers change Create or edit a changelist description changes Display list of pending and submitted changelists changelist Create or edit a changelist description changelists Display list of pending and submitted changelists client Create or edit a client specification and its view clients Display list of known clients copy Schedule copy of latest rev from one file to another configure Set, unset, or show server configuration variables counter Display, set, or delete a counter counters Display list of known counters dbschema Report information about metadata in the Perforce database. dbstat Display size or simple statistics for a database table delete Open an existing file to delete it from the depot depot Create or edit a depot specification depots Display list of depots describe Display a changelist description diff Display diff of client file with depot file diff2 Display diff of two depot files dirs List subdirectories of a given depot directory edit Open an existing file for edit export Extract journal or checkpoint records filelog List revision history of files files List files in the depot fix Mark jobs as being fixed by named changelists fixes List what changelists fix what job flush Fake a 'p4 sync' by not moving files fstat Dump file info grep Print lines from text files matching a pattern group Change members of a user group groups List groups (of users) have List revisions last synced help Print the requested help message info Print out client/server information integrate Schedule integration from one file to another integrated Show integrations that have been submitted job Create or edit a job (defect) specification jobs Display list of jobs jobspec Edit the job template label Create or edit a label specification and its view labels Display list of labels labelsync Synchronize label with the current client contents license Update or display the license file lock Lock an opened file against changelist submission lockstat Report lock status of database tables logger Report what jobs and changelists have changed login Login to Perforce by obtaining a session ticket logout Logout of Perforce by removing or invalidating a ticket. logstat Report size of journal/errorLog/auditLog files logtail Display the last block(s) of the errorLog monitor Display current running perforce process information move Moves files from one location to another obliterate Remove files and their history from the depot opened Display list of files opened for pending changelist passwd Set the user's password on the server (and Windows client) ping Test network performance print Retrieve a depot file to the standard output protect Modify protections in the server namespace protects Display protections in place for a given user/path pull Cause satellite to pull journal or file data from master rename Explains how to rename files reopen Change the type or changelist number of an opened file replicate Poll for journal changes and apply to another server resolve Merge open files with other revisions or files resolved Show files that have been merged but not submitted restore Restore archived revisions to their original location. revert Discard changes from an opened file review List and track changelists (for the review daemon) reviews Show what users are subscribed to review files set Set variables in the registry (Windows only) shelve Store files from a pending changelist into the depot sizes Display size information for files in the depot submit Submit open files to the depot sync Synchronize the client with its view of the depot tag Tag files with a label tickets Display list of session tickets for this user triggers Modify list of server triggers typemap Modify the file name-to-type mapping table unlock Release a locked file but leave it open unshelve Restore shelved files from a pending changelist user Create or edit a user specification users Display list of known users verify Verify that the server archives are intact workspace Create or edit a client specification and its view workspaces Display list of known clients where Show how file names map through the client view @ @pv@ 0 @db.message@ @en@ 268445711 @ Unsupported or obsolete Perforce commands and options: p4 admin dump Outputs a checkpoint of the server through the client. Important: read-locks the database during the entire operation! Normally database locks are not held during network I/O to the client. p4 admin import [-l] [-b batchsz] Imports a journal of the server through the client. The journal data is read from the standard input. When the data has been transfered to the server, it is processed in batches with the batch size of 5000 records or the number specified with the '-b' flag. Each batch locks only the tables that will change. The -l flag instructs import to write-lock all database tables and processes all data until it comes to the end of the file or encounters an error. When applying records to the database, it ignores failures to delete records, unlike 'p4d -jr', which normally terminates if it can't delete a record as indicated by the journal. Avoid using this command to import large journal files, because the entire file has to fit in memory. p4 attribute Set per-revision attributes on revisions. See 'p4 help attribute'. p4 configure show env Displays the command-line flags and environment variables that were in effect when this server was started. p4 configure show undoc Displays a list of all the server tunable parameters and their current values. Consult Perforce Technical Support before changing values. p4 cstat Dump change/sync status for current client. See 'p4 help cstat'. p4 dbpack Reorder database index pages. See 'p4 help dbpack' p4 diff/diff2/describe -dh The -dh compares files on a word-by-word basis (using whitespace as a separator rather than just newline), and marks differences with HTML tags that switch the font to red or blue for words that are only in the first or second file, respectively. p4 diff/diff2/describe -dv The -dv compares files on a word-by-word basis (using character classes rather than just newline), and marks differences with HTML tags that switch the font to red or blue for words only in the first or second file, respectively. p4 duplicate Duplicate revisions and their integration history. See 'p4 help duplicate'. p4 get Old name for 'p4 sync'. p4 filelog -1 This flag prevents filelog from following any renames resulting from use of the 'p4 move' command. By default, filelog follows moved files. p4 fstat [-Oacedhiz] [-A pattern] The -Oa flag displays attributes set by 'p4 attribute'. The -Oae flag displays the attribute values encoded as hex. The -Od flag outputs the digest of the attribute. The -Oc flag outputs the path, revision and type of the server archive file (requires 'admin' privilege). The -Oz flag outputs the path and revision of any lazy copies (requires 'admin' privilege). The -Oh flag outputs the size, digest and any selected attributes of the synced revision rather than the head revision. The -Oi flag outputs extra (debugging) information about the attributes. The -A pattern flag restricts attributes to those matching 'pattern'. p4 groups [-g | -u | -o] name The -g flag indicates that the 'name' argument is a group, the -u flag indicates that the 'name' argument is a user, and the -o flag indicates that the 'name' argument is an owner. These flags are useful when there are groups and users with the same name. The -o flag is useful for requesting all groups owned by 'name'. p4 help commandments Values we work by. p4 help credits Lists server contributors. p4 index Add words to the jobs index. See 'p4 help index'. p4 interchanges Report changes that have not yet been integrated. See 'p4 help interchanges'. p4 integrate -1 -3 -I -C changelist# The flag '-1' forces the integrate command to consider only direct integration history only. The -I flag used to turn on indirect integration; that behavior is now the default and only implies -i now. The -C changelist# flag considers only integration history from changelists at or below the given number, enabling you to ignore credit from subsequent integrations. The -3 flag uses the experimental 'third generation' integrate engine, new to 2009.1 (see following entry for additional information). p4 integrate -3 -Mbdo -Rs The '-3' engine is designed to produce more accurate results than the current engine, and is intended to replace it in an upcoming release. By default, 'integrate -3' detects target files that have been previously moved with 'p4 move', and automatically 'retargets' itself to follow those move operations. The '-M' flag modifies this: -Mb : only retarget within branch/toFile view -Md : retarget when source is deleted -Mo : disable retargeting (old behavior) The '-3' engine also provides an alternative to the default behavior of scheduling a single resolve per file: -Rs : split resolves around previously-integrated revisions p4 interchanges -3 Derives interchanges results from the results of 'integrate -3 -Rs'. p4 jobspec presets Preset values for job non-optional fields that undergo variable expansion, in addition to the simple $now, $blank, and $user substitution. The variables supported include: %%old%% (previous contents of field), %%action%% (what caused the update of the form), %%n%% (a newline), %%date%% (date and time), %%day%% (date only), and %%user%%. p4 jobspec codes over 10000 Jobspec field codes are required to be in the range 100-199 or over 10000. p4 obliterate [-abh] Obliterate has three flags that can improve performance: The '-b' flag restricts files in the argument range to those that are branched and are both the first revision and the head revision This flag is useful for removing old branches while keeping files of interest (files that were modified). The '-a' flag skips the archive search and removal phase. This phase of obliterate can take a very long time for sites with big archive maps (db.archmap). However, file content is not removed; if the file was a branch, then it's most likely that the archival search is not necessary. This option is safe to use with the '-b' option. The '-h' flag instructs obliterate not to search db.have for all possible matching records to delete. Usually, db.have is one of the largest tables in a repository and consequently this search takes a long time. Do not use this flag when obliterating branches or namespaces for reuse, because the old content on any client will not match the newly-added repository files. p4 merge3 Three-way file merge. See 'p4 help merge3'. p4 obliterate [ -iI ] Tells obliterate to synthesize new integration records to attempt to bridge the gaps left by the obliteration of intermediate branches. If '-i' is used, only the initial branch records are considered; if '-I' is used, all records are considered. Note that it is possible to end up with more integration records than you started with. p4 refresh files... Old name for 'p4 sync -f #have'. p4 reresolve Old name for 'p4 resolve -f'. p4 resolve -dg The'-dg' flag makes the default merge algorithm more guarded about merging adjacent chunks. When this option is specified, more conflicts are returned, especially where changes in both 'yours' and 'theirs' are identical but then diverge. p4 resolve -e Translates all 'ignored' results to 'edit from', leaving the contents unchanged. The resulting revision is a candidate for integration back to its source, which has the effect of undoing the 'ignored' change. p4 retype Change revision or server archive type. See 'p4 help retype'. p4 search Search index. See 'p4 help search'. p4 snap Snap archive lazy copies. See 'p4 help snap'. p4 spec Edit spec definitions. See 'p4 help spec'. p4 submit -t Tamper-checks branch/sync files and files resolved with 'at' (copy from/lazy-copied files). This check can significantly slow submit. Imported files are never tamper-checked. p4 trigger 'auth-check-sso' The trigger type 'auth-check-sso' can be used to facilitate a single sign-on user authentication. Two programs or scripts are required with this configuration: client: Set the environment variable 'P4LOGINSSO' to point to a script that can be executed to obtain the user's credentials or other information that the server-side trigger can verify. The script must write the message to the standard output (max length 128K). Example: P4LOGINSSO = /Users/joe/bin/runsso The 'server address' can be optionally passed to the client script by appending %%serverAddress%% to the client command string, as in: P4LOGINSSO = "/Users/joe/bin/runsso %%serverAddress%%" server: Execute an authentication (sso) trigger that gets this message from the standard input and returns an exit status of 0 (for verified) or otherwise failed. Example: sso auth-check-sso auth "/secure/verify %%user%%" The user must issue the 'p4 login' command, but no password prompting is necessary. If the server determines that the user is valid, they are issued a Perforce ticket just as if they had logged in with a password. Pre-2007.2 clients cannot run a client-side single sign-on. Specifying an 'auth-check' trigger as a backup for a user to gain access will prompt the user for a password if it's an older client or P4LOGINSSO has not been configured. Unlike passwords which are encrypted, the sso message is sent to the server in clear text. p4 where -Ttag Output text in the 'tagged' format generated by 'p4 fstat'. Predefined Trigger Actions The predefined trigger actions 'pass' and 'fail' are processed by the server without calling any external scripts. 'pass' will always succeed. 'fail' will always fail and return the expanded argument list as the error message. Relative revisions @@<, @@<=, @@>, @@>=, @@= and #<, #<=, #>, #>=, #= Anywhere a revision range can be specified, the revisions can be modified with relative operators. Relative operators on #head (other than = and <=) aren't supported. A maximum of 4 revision specifications (separated by ,s) are allowed: the implied operator on the first is >=; thereafter <=. You must quote < and > for the command-line shell. See 'p4 help revisions' for a description of revision specifications. Revision actions #add, #edit, #delete, #branch, #integrate, #import Selects all revisions with the specified action. Actions are not relative, which means that #action cannot be used in a revision range. For many commands, when multiple revisions of the same file are selected, the highest revision is used. FileType modifier +T The +T modifier stores the revisions in the server in a database file called tiny.db, which is useful for lots of very small files. There is no special support for separately backing up or restoring this file. The types ttext and tbinary are equivalent to text+T and binary+T. Jobspec format The 'p4 jobspec' form can have an additional field 'Formats:' to help Perforce visual clients display forms properly. Each row of the Format field consists of three words: field, order, and format. The order is an integer (starting at 1) indicating the display order (the display order is otherwise undefined). The format is: normal, L, R, or I; for full line, left half, right half, indented. If a right field follows a left, they are displayed on the same line. JobStatus field on 'p4 change', 'p4 submit' 'p4 change' and 'p4 submit' forms have a 'JobStatus' field that is not normally displayed. This field sets the fix status for all jobs, overriding the default (which is 'closed'). A job's fix status can be set using the 'p4 change -s' and 'p4 submit -s' commands. p4 -zmaxLockTime=n command p4 -zmaxResults=n command p4 -zmaxScanRows=n command Overrides the user's maxLockTime/maxResults/maxScanRows for the command. p4 -e Extended version of the '-s' output that displays more detailed information about each error/info message received, including the formatting strings, unique error codes, and severity values that are available to API users. p4 -E P4VAR=value Override the value of an arbitrary environment/config variable, as in a P4CONFIG file. Multiple instances of this flag can be used. Useful for variables without dedicated override flags (such as P4DIFF). p4 -R Formats all output (and batch input for form commands with -i) as marshalled Ruby hash objects. p4d -Cn Forces the server to operate in case-sensitive mode (n=0) on Windows or case-insensitive mode (n=1) on Unix. n=2 is an experimental 'hybrid' order that folds case while preserving uniqueness. Changing Attempting to change modes after a database is created produces an error. p4d -cshow Displays the contents of the db.config table, similar to the output of 'p4 configure show allservers', but can be run when the server is down. p4d -s -jr journal The '-s' flag directs the recovery process to journal recovered records into the server's journal file. The '-J journal' flag to set the journal file works with this. These records might have their order changed, and transaction markers will differ to reflect batching and the transaction that performed the recovery. p4d -jrc journal Increases the size of each batch of journal records until a marker is seen indicating that all transactions are complete, then locks only the database tables that will be changed, applies the changes, then unlocks the tables. This approach provides consistent database updating and allows the system to be used while a journal is being applied. p4d -jds dumpfile Dumps the server metadata to the specified file. Unlike p4d -jd, ignores the table indexes and reads in file system order rather than data order. This option can be useful for recovery if the btree index structure becomes corrupt. This recovery procedure is not meant for normal production operation. Restoring the resulting dump file does not compact the btrees as effectively as restoring from regular checkpoints does, and such restores take longer to complete. p4d -xf bugno Updates the server data to fix problems due to the specified bug number. Valid values of bugno are as follows: 925 -- working and locks table out of sync 3104 -- early 99.2 resolve bug 4164 -- early 2000.1 submit bug 12904 -- replace / with _ in client names 18362 -- 2005.2 replace 'check' trigger command p4d -xU upgrade Re-runs the named upgrade step that is normally done automatically by p4d -xu. To display a list of steps, issue the 'p4d -xU help' command. This option can be used to rebuild certain tables (like db.archmap). p4d -xx [table1 [table2]] Checks consistency between table pairs, producing a file jnl.fix with '@@dv@@' and '@@pv@@' records which, when read in with p4d -jr, eliminate any inconsistencies. If table names are specified, only those tables are checked. Check the jnl.fix file for accuracy before attempting any updates. p4d -xv Does a low-level verification of database files. p4d -xr Does a low-level verification and repair of database files. Use only as a last resort if checkpoint and journal are not available. p4d -f -jr files... The -f flag directs the journal restoration process to ignore failures to delete records (such failures occur as a result of corrupted tables or using the wrong journal). By default, journal restoration halts if record deletion fails. p4d -b bunchLen -jr files... The -b bunchLen causes the server to read bunchLen journal records at a time, sorting them and removing duplicates before updating the database. Default value is 5000. To force serial processing (the pre-2005.1 behavior), specify -1. p4d -p -jd The -p flag directs the server to dump metadata in a form compatible with an older server version. The earliest version that might work is 2005.1, which is server level 19. p4d -m rcsfiles... Dumps RCS metadata from files to a format suitable for the CVS-to-Perforce conversion script. p4p -k ... Start the Perforce Proxy without cache timestamp checking. The Perforce Proxy normally uses a timestamp on cached revisions to check that the right revision is delivered if an obliterate deletes a revision that is subsequently replaced with an identically- numbered revision. Using this option causes problems if head revisions are obliterated. However, the proxy cache can be pre- loaded loaded with the server's archive files by specifying this flag when you start the proxy. p4p -w ... Start the Perforce Proxy in read-only cache mode. In this mode the proxy never updates its cache, which is useful if the cache is updated through a WAN NFS or other system-level remote filesystem method. P4AUTH=central-server-address P4AUTH functionality is now fully supported for 2010.2, see the System Administration Guide for more details. P4CHANGE=central-server-address P4CHANGE functionality is now fully supported for 2010.2, see the System Administration Guide for more details. P4LOG=syslog Uses syslog instead of the named error log file for server error logging. Must be set in server's environment. P4DEBUG=server=1 Logs server commands to the file configured by P4LOG. The server=2 option logs command completion. Must be set in server's environment. Perforce server configurables (unsupported) P4DEBUG=configurables For information about supported server configuration variables, see 'p4 help configurables'. The following server parameters can be tuned using 'p4 configure set' or by setting P4DEBUG to a list of variable=value pairs separated by commas. Change these values only as directed by Technical Support. Values that are too large or small are silently corrected. Name Default Use ---- ------- --- db.isalive 10K Rows scanned before maxLockTime check db.trylock 3 Attempts to avoid locks that block dbarray.putcheck 4K Every this many rows... dbarray.reserve 4M ...make sure we have this much memory dbjournal.wordsize 4K Journal word processing size dbopen.cache 96 Pages of cache for db.* files dbopen.cache.wide 192 Pages of cache for db.integed dbopen.freepct 0 Free page space on p4d -jr dbopen.pagesize 8K Page size of db.* files diff.slimit1 10M Longest diff snake; smaller is faster diff.slimit2 100M Longest diff snake for smaller files diff.sthresh 50K Use slimit2 if lines to diff < sthresh dm.batch.domains 0 'labels path' scan in label intervals dm.changes.thresh1 50K 'changes -mx path' uses db.revcx if... dm.changes.thresh2 10K ...if < thresh2 of thresh1 db.rev match dm.flushforce 10K Flushtry can expand until forced dm.flushtry 100 Update buffer for sync, resolve, edit dm.grep.maxlinelength 4096 Maximum line length that can be searched dm.grep.maxcontext 1K Maximum size of context allowed for grep dm.integ.maxact 100K Max db.integed edges considered for a file dm.isalive 50K Rows scanned before client connection check dm.maxkey 1K Longest identifier (client, label, etc) dm.quick.clients 10M Release lock if all needed rows buffered dm.quick.domains 1M Release lock if all needed rows buffered dm.quick.have 1M Release lock if all needed rows buffered dm.quick.integ 1M Release lock if all needed rows buffered dm.quick.resolve 1K Release lock if all needed rows buffered dm.quick.rev 100K Release lock if all needed rows buffered dm.quick.working 1K Release lock if all needed rows buffered dm.revcx.thresh1 4K Path@@change uses db.revcx if thresh2 ... dm.revcx.thresh2 1K ...of thresh1+thresh2 rows match path filesys.maketmp 10 Max attempts to find unused temp name filesys.maxmap 1000M Use read rather than mmapping big files filesys.maxsymlink 1K Symlink maximum content length filesys.maxtmp 1M Rollover for creating temp file names map.joinmax1 10K Produce at most map1+map2+joinmax1 map.joinmax2 1M Produce at most joinmax2 map.maxwild 10 Maximum number of wildcards per line net.bufsize 4K Network I/O buffer size rcs.maxinsert 1G Max lines in RCS archive file rpc.himark 2000 Max outstanding data between server/client rpc.lowmark 700 Interval for checking outstanding data spec.custom 0 If > 0 allow modifications to spec forms. @ @pv@ 0 @db.message@ @en@ 268445712 @ Environment variables used by Perforce: Variable Defines More information -------- ------- ------------------------ P4CHARSET Client's local character set p4 help charset P4COMMANDCHARSET Client's local character set (for command line operations) p4 help charset P4CLIENT Name of client workspace p4 help client P4CLIENTPATH Directories client can access Perforce Command Reference P4CONFIG Name of configuration file Perforce Command Reference P4DIFF Diff program to use on client p4 help diff P4DIFFUNICODE Diff program to use on client p4 help diff P4EDITOR Editor invoked by p4 commands p4 help change, etc P4HOST Name of host computer p4 help usage P4LANGUAGE Language for text messages p4 help usage P4MERGE Merge program to use on client p4 help resolve P4MERGEUNICODE Merge program to use on client p4 help resolve P4PAGER Pager for 'p4 resolve' output p4 help resolve P4PASSWD User password passed to server p4 help passwd P4PORT Port to which client connects p4 help info P4TICKETS Location of tickets file Perforce Command Reference P4USER Perforce user name p4 help usage PWD Current working directory p4 help usage TMP, TEMP Directory for temporary files Perforce Command Reference For details about configuring Windows settings, issue the 'p4 help set' command. The syntax for setting an environment variable depends on the OS/shell. Many shells permit you to set shell variables separately from environment variables, but Perforce cannot access the shell variable, only the environment variable. Variables of primary interest to typical users are: $P4CLIENT, $P4PORT and $P4PASSWD. Environment variables used by the Perforce server: Variable Defines More information -------- ------- ------------------------ P4AUDIT Name of server audit file p4d -h P4AUTH Authentication server address System Admin Guide P4CHANGE Global changelist server address System Admin Guide P4DESCRIPTION Text description for server p4 help zeroconf P4JOURNAL Name of server journal file p4d -h P4LOG Name of server log file p4d -h P4NAME Unique server name p4 help zeroconf P4PORT Port on which server listens p4d -h P4ROOT Server root directory p4d -h P4TARGET Target server for proxy/replica Perforce Command Reference P4TICKETS Location of tickets file Perforce Command Reference P4ZEROCONF Register with Zeroconf p4 help zeroconf TMP, TEMP Directory for temporary files Perforce Command Reference To set server environment variables persistently, use the 'p4 configure' command. Note that P4ROOT and TMP/TEMP cannot be set using 'p4 configure'. @ @pv@ 0 @db.message@ @en@ 268445713 @ File types supported by Perforce: Perforce file type determines how the file is handled on both the client and the server. A filetype can be specified as 'type', with modifiers as 'type+mods' or as just the modifiers '+mods'. The following are the base Perforce filetypes: Type Client Use Server Storage ---- ---------- -------------- text newlines translated deltas in RCS format binary raw bytes compressed binary symlink symbolic link deltas in RCS format apple Mac resource + data compressed AppleSingle resource Mac resource fork compressed binary unicode newlines translated deltas in RCS format stored as UTF-8 utf16 newlines translated deltas in RCS format client file UTF-16 stored as UTF-8 in client byte order unless BOM overrides File is always written with a BOM A BOM is needed for automatic type detection The following are the modifiers: Modifier Meaning -------- ------- +m always set modtime on client (overrides client's nomodtime) +w always writable on client +x exec bit set on client +k $Keyword$ expansion of Id, Header, Author Date, DateTime, Change, File, Revision +ko $Keyword$ expansion of ID, Header only +l exclusive open: disallow multiple opens +C server stores compressed file per revision +D server stores deltas in RCS format +F server stores full file per revision +S server stores only single head revision +S server stores number of revisions, where is a number 1-10 or 16,32,64,128,256,512. +X server runs archive trigger to access files The following aliases for filetypes are supported for backwards compatibility: Type Is Base Type Plus Modifiers -------- ------------ -------------- ctempobj binary +Sw ctext text +C cxtext text +Cx ktext text +k kxtext text +kx ltext text +F tempobj binary +FSw ubinary binary +F uresource resource +F uxbinary binary +Fx xbinary binary +x xltext text +Fx xtempobj binary +Swx xtext text +x xunicode unicode +x xutf16 utf16 +x 'p4 add', 'p4 edit', and 'p4 reopen' accept the '-t filetype' flag to specify the filetype. If you omit the -t flag, 'p4 add' determines filetype using its own logic and the name-to-type mapping table managed by 'p4 typemap', if configured. By default, 'p4 edit' and 'p4 reopen' reuse the current file filetype, and 'p4 add' determines the filetype by examining the file's contents and its execute permission bits. If a filetype is specified using only '+mods, then that filetype is combined with the default. Most modifiers are simply added to the default type, but the +C, +D, and +F storage modifiers replace the storage method. To remove a previously assigned modifier, the whole filetype must be specified. @ @pv@ 0 @db.message@ @en@ 268445714 @ Perforce job views: A job view is an expression that selects jobs according to word and date matches. Job views are used by the 'p4 jobs' -e flag to select the jobs to be displayed. The 'p4 user' form contains a JobView field, which selects the jobs that are added to newly- created changelists. 'p4 job' indexes all whitespace-separated words and all punctuation- separated words within those words. So 'sub-par' is entered into the index as 'sub', 'par', and 'sub-par'. Case is not considered. 'p4 job' separately indexes all date fields in a way that enables you to search for a range of dates. In its simplest form, a job view is a list of words separated by spaces, used to select jobs. For a match to occur, all the specified words must appear somewhere in the job, except for date fields: JobView: GUI redrawing bug p4 jobs -e 'GUI redrawing bug' To match the contents of a particular field, use the 'field=word' syntax: JobView: GUI redrawing status=open Logical operators & (and), | (or), ^ (not), and () (grouping) can also be used. Spaces are treated as a low-precedence 'and' operator: JobView: redrawing (type=bug|type=sir) status=open The ^ (not) operator can be used only in conjunction with the & (and) or space (and) operators: JobView: type=bug & ^status=closed The comparative operators >, >=, <, <=, and = succeed if any word in the field matches, so only the = operator is useful for matching fields that contain blocks of text: JobView: priority<=b description=gui Text searches can use the * wildcard, which matches anything: JobView: redraw* type=bug To match operator characters, escape them with \. Date fields can be searched using comparative operators. Specify dates using the format yyyy/mm/dd or yyyy/mm/dd:hh:mm:ss. If you omit the time, the equality operators (=, <=, >=) match the whole day: JobView: reported_date>=1998/01/01 status=closed Text field comparisons are done alphabetically. Date field comparisons are done chronologically. @ @pv@ 0 @db.message@ @en@ 268445715 @ Specifying file revisions and revision ranges: You can limit the effect of some commands to a single file revision or a range of revisions, by appending one of the following revision specifiers to the file specification: #rev - A revision number or one of the following keywords: #none - A nonexistent revision (also #0). #head - The current head revision (also @@now). #have - The revision on the current client. @@change - A change number: the revision as of that change. @@client - A client name: the revision on the client. @@label - A label name: the revision in the label. @@date - A date or date/time: the revision as of that time. Either yyyy/mm/dd or yyyy/mm/dd:hh:mm:ss Note that yyyy/mm/dd means yyyy/mm/dd:00:00:00. To include all events on a day, specify the next day. Only matching revisions are processed. If you use a label to refer to a file that the label doesn't contain, the file is not processed. If you omit the revision specification, the default is usually #head. If you specify a revision or range and omit the file specification, the command affects all relevant files. For example, #head refers to the head revision of all files in the depot, and @@label refers to the revisions of all files in the specified label. Some commands accept a range of revisions, specified as the start and end revisions separated by a comma. If a single revision is specified where a revision range is expected, the revision specifies the end revision, and the start defaults to revision #1. 'p4 obliterate' is an exception: a single revision means only that revision. If you omit the revision specifier, the default is all revisions. @ @pv@ 0 @db.message@ @en@ 268445716 @ Perforce views: A Perforce view maps file names from the depot to the client workspace (client view) or to another part of the depot (branch view). A view is one or more mappings, and each mapping is a pair of file names on a line. The left side always refers to the depot namespace; the right side refers to the client or depot namespace. Each name is in Perforce syntax: it begins with //, followed by the client or depot name, then the file name. If the path contains whitespace, it must be double-quoted. Perforce syntax uses forward slashes (/) as directory separators. Example: "//depot/a dir/file.c" Mappings can contain wildcards. Wildcards on the right and left sides of a mapping must match. Valid wildcards are: * Matches any characters except / ... Matches any characters, including / %%%%1 to %%%%9 Like *, but used to reorder the path If more than one mapping line refers to the same files, the later mapping line overrides the earlier one. A mapping line that begins with a + overlays the later mapping on an earlier one: if files match both the earlier and later mappings, then the file matching the later mapping is used. Overlay mappings are supported only for client views, and enable you to map multiple server directories to the same client directory. To exclude matching files, precede the mapping with a minus sign (-). @ @pv@ 0 @db.message@ @en@ 268445717 @ Limiting data access: To avoid swamping servers with requests that result in large datasets, the Perforce super-user can limit the amount of data that the server handles for client operations. The following limits can be set: MaxResults, MaxScanRows, and MaxLockTime. If an operation exceeds any of these limits, the whole operation fails. MaxResults limits the number of rows of result data buffered and prevents the server from using excessive memory. MaxScanRows limits the number of rows of data considered and prevents the server from making large-scale scans. MaxLockTime limits the amount of time spent during data scans to prevent the server from locking tables for too long. MaxLockTime starts counting when the first table is locked, and includes time spent waiting for any subsequent table locks. To set limits for groups of users, issue the 'p4 group' command. For naive users, set MaxResults to a value that is larger than the number of files likely to reside in any of their client workspaces Set MaxScanRows to MaxResults multiplied by the average number of revisions per file in the repository. As a rule, neither need to be smaller than 10000 or 50000 (respectively), and values of 50000 and 250000 are probably sufficient to prevent accidental misuse without interfering with normal use. Set MaxLockTime to a value in the 1000-30000 (1-30 second) range. The following table lists the commands that are controlled by these limits, the entity that is counted, and tells you how to adjust the operation to run within the limit. Command Counting Reduce output with: ------- -------- ------------------- p4 add files * see (1) p4 annotate revisions see (2) p4 changes changes -m maxChanges p4 changes files revisions see (2) p4 delete files * see (1) p4 describe files * see (3) p4 diff files * see (1) p4 diff2 files see (1) p4 dirs files * see (1) p4 edit files * see (1) p4 filelog revisions see (2) p4 files files see (1) p4 fixes fixes -j job, -c change p4 fixes files revisions see (2) p4 fstat files see (1) p4 integrate files see (1) p4 integrated revisions see (2) p4 jobs jobs -e query p4 jobs files revisions see (2) p4 have files * see (1) p4 labels files files * see (1) p4 labelsync files see (4) p4 lock files * see (1) p4 obliterate revisions * see (2) p4 opened files * see (1) p4 print files see (1) p4 revert files * see (1) p4 reopen files * see (1) p4 resolve files * see (1) p4 resolved revisions * see (2) p4 reviews -c revisions * see (2) p4 sync files see (1) p4 verify revisions -m maxRevs * Subject to MaxScanRows/MaxLockTime but not MaxResults. (1) These commands limit files. Use more restrictive wildcards. (2) These commands limit individual revisions of each file, which can significantly exceed the number of actual files. Restrict the operation by using more restrictive wildcards on the command line to exclude more files, or by using a revision range (if permitted). (3) If the data required to describe a change exceeds the limit, 'describe cannot be run. (4) 'labelsync' limits files. To build up the label in pieces, use restrictive wildcards with 'p4 labelsync -a'. @ @pv@ 0 @db.message@ @en@ 268445719 @ The Perforce clients and server have an optional mode of operation in which all metadata and some file content are stored in the server in the UTF8 Unicode character set and are translated into another character set on the client. The environment variable P4CHARSET specifies the client character set. Valid settings for P4CHARSET are: eucjp iso8859-1 iso8859-5 iso8859-15 macosroman shiftjis koi8-r utf8 (UTF-8) utf8-bom (UTF-8 with Byte-Order-Mark) utf16 (UTF-16 with client's byte ordering and Byte-OrderMark) utf16-nobom (UTF-16 client's byte ordering without Byte-Order-Mark) utf16le (UTF-16 with little endian byte ordering) utf16le-bom (UTF-16 with little endian Byte-Order-Mark) utf16be (UTF-16 with big endian byte ordering) utf16be-bom (UTF-16 with big endian Byte-Order-Mark) utf32 (UTF-32 with client's byte ordering and Byte-OrderMark) utf32-nobom (UTF-32 client's byte ordering without Byte-Order-Mark) utf32le (UTF-32 with little endian byte ordering) utf32le-bom (UTF-32 with little endian Byte-Order-Mark) utf32be (UTF-32 with big endian byte ordering) utf32be-bom (UTF-32 with big endian Byte-Order-Mark) cp949 (Windows code page 949 - Korean) cp1251 (Windows code page 1251 - Cyrillic) winansi (Windows code page 1252) none (same as unsetting P4CHARSET) If (and only if) P4CHARSET is set for the client, the server must also be operating in Unicode mode. This mode is switched on (and never off) by invoking 'p4d -xi' on the server. This operation verifies that all existing metadata is valid UTF8, and then sets the protected counter 'unicode' to indicate that the server now runs in Unicode mode. In Unicode mode, all non-file data (identifiers, descriptions, etc) and the content of files of type 'unicode' are translated between the character set configured on the client by P4CHARSET and UTF8 in the server. P4CHARSET is supported by 2001.2 and later clients. When P4CHARSET is set to one of the UTF-16 values, P4COMMANDCHARSET must be set to a non-utf-16 value for the p4 command-line client to operate correctly. This configuration enables P4CHARSET to control the translation of file revision contents while using a command line system that is not utf-16 based (because most command lines are not utf-16 compatible). All UTF-16 values honor a file's Byte- Order-Mark when a file is read. When a file is written, the specified UTF-16 format is observed. @ @pv@ 0 @db.message@ @en@ 268445824 @ P4 Commandments -- Values we work by * We have high standards. * We are straightforward. * We rise to responsibility. * We like work we can be proud of. * We like to hear what we've done. * We value both people and job skills. * We treat each other with dignity and respect. * We are one team. We are not in competition with each other. * We talk and listen. We like feedback. * We appreciate creative and practical solutions. There might be a better way. * We appreciate people for who they are. * Fun is always an option. It is not mandatory. * These are the best years of our lives. @ @pv@ 0 @db.message@ @en@ 268445720 @ Perforce, The Fast Software Configuration Management System, from the fleet fingers of Christopher Seiwald, with notable contributions from Jeff Anton, Michael Bishop, Brian Campbell, Geri Clucas, Cal Collier, Sven Knop, Peter Kreps, Mark Mears, Michael Alyn Miller, Bryan Pendleton, Mike Schonberg, Andy Shebanow, David Sielaff, Tony Smith, Sam Stafford, James Strickland, and Alan Teague. @ @pv@ 0 @db.message@ @en@ 268445721 @ add -- Open a new file to add it to the depot p4 add [-c changelist#] [-d -f -n] [-t filetype] file ... Open a file for adding to the depot. If the file exists on the client, it is read to determine if it is text or binary. If it does not exist, it is assumed to be text. To be added, the file must not already reside in the depot, or it must be deleted at the current head revision. Files can be deleted and re-added. To associate the open files with a specific pending changelist, use the -c flag; if you omit the -c flag, the open files are associated with the default changelist. If file is already open, it is moved into the specified pending changelist. You cannot reopen a file for add unless it is already open for add. As a shortcut to reverting and re-adding, you can use the -d flag to reopen currently-open files for add (downgrade) under the following circumstances: A file that is 'opened for edit' and is synced to the head revision, and the head revision has been deleted (or moved). A file that is 'opened for move/add' can be downgraded to add, which is useful when the source of the move has been deleted or moved. Typically, under these circumstances, your only alternative is to revert. In this case, breaking the move connection enables you to preserve any content changes in the new file and safely revert the source file (of the move). To specify file type, use the -t flag. By default, 'p4 add' determines file type using the name-to-type mapping table managed by 'p4 typemap' and by examining the file's contents and execute permission bit. If the file type specified by -t or configured in the typemap table is a partial filetype, the resulting modifier is applied to the file type that is determined by 'p4 add'. For more details, see 'p4 help filetypes'. To add files with filenames that contain wildcard characters, specify the -f flag. Filenames that contain the special characters '@@', '#', '%' or '*' are reformatted to encode the characters using ASCII hexadecimal representation. After the files are added, you must refer to them using the reformatted file name, because Perforce does not recognize the local filesystem name. The -n flag displays a preview of the specified add operation without changing any files or metadata. @ @pv@ 0 @db.message@ @en@ 268445722 @ admin -- Perform administrative operations on the server p4 admin checkpoint [-z] [prefix] p4 admin journal [-z] [prefix] p4 admin stop p4 admin updatespecdepot [-a | -s type] 'p4 admin checkpoint' causes the server to take a checkpoint and to copy the journal to a numbered journal file. This command is equivalent to 'p4d -jc'. 'p4 admin journal' causes the server to save the journal to a numbered journal file and then truncate it. This command is equivalent to 'p4d -jj'. The -z flag saves the checkpoint and journal in compressed (gzip) format, with the '.gz' extension added to the file names. If a prefix is specified, the files are named prefix.ckp.n and prefix.jnl.n respectively, where n is a sequence number. Without a prefix, the default filenames are checkpoint.n and journal.n. 'p4 admin stop' stops the server, terminating any requests currently running. It locks the database to ensure that no updates are taking place, but otherwise does not wait for users to finish what they are doing. (Windows NT: this command can be used regardless of whether you are running the server as a program or a service.) 'p4 admin updatespecdepot' archives forms (client, depot, branch, label, typemap, group, user, job) into the spec depot. To archive all types of form specifications specify the -a flag. To archive a single type of spec, specify the '-s' flag. Only forms that have not yet been archived are created. @ @pv@ 0 @db.message@ @en@ 268445723 @ branch -- Create or edit a branch specification and its view p4 branch [-f] name p4 branch -d [-f] name p4 branch -o name p4 branch -i [-f] Create a new branch specification or edit an existing branch specification. The specification form is put into a temporary file and the editor (configured by the environment variable $P4EDITOR) is invoked. The branch specification form contains the following fields: Branch: The branch name (read only). Owner: The user who created this branch. Can be changed. Update: The date specification was last modified. Access: The date of the last 'integrate' using this branch. Description: A short description of the branch (optional). Options: Flags to change the branch behavior. The defaults are marked with *. locked Permits only the branch owner to change its unlocked * specification. Prevents the branch from being deleted. View: A mapping from the source files of the branch to the target files of the branch. Both the left and right- hand sides of the mappings refer to the depot namespace. See 'p4 help views' for more on views. New branch specs are created with a default view that maps all depot files to themselves. This view must be changed before the branch view can be used. Branch specs are used only by the 'p4 integrate' command. The -d flag deletes the named branch. The -o flag writes the branch specification to standard output. The user's editor is not invoked. The -i flag reads a branch specification from the standard input. The user's editor is not invoked. The -f flag enables a user with 'admin' privilege to delete the spec or set the 'last modified' date. By default, specs can be deleted only by their owner. @ @pv@ 0 @db.message@ @en@ 268445783 @ annotate -- Print file lines and their revisions p4 annotate [-aciIq -d] file[revRange] ... Prints all lines of the specified files, indicating the revision that introduced each line into the file. If the file argument includes a revision, then only revisions up to the specified revision are displayed. If the file argument has a revision range, only revisions within that range are displayed. For details about specifying revisions, see 'p4 help revisions'. The -a flag includes both deleted files and lines no longer present at the head revision. In the latter case, both the starting and ending revision for each line is displayed. The -c flag directs the annotate command to output changelist numbers rather than revision numbers for each line. The -d change the way whitespace and/or line endings are treated: -db (ignore whitespace changes), -dw (ignore whitespace), -dl (ignore line endings). The -i flag follows branches. If a file was created by branching, 'p4 annotate' includes the revisions of the source file up to the branch point, just as 'p4 filelog -i' does. If a file has history prior to being created by branching (such as a file that was branched on top of a deleted file), -i ignores those prior revisions and follows the source. -i implies -c. The -I flag follows all integrations into the file. If a line was introduced into the file by a merge, the source of the merge is displayed as the changelist that introduced the line. If the source itself was the result of an integration, that source is used instead, and so on. -I implies -c. The -q flag suppresses the one-line header that is displayed by default for each file. @ @pv@ 0 @db.message@ @en@ 268445821 @ archive -- Archive obsolete revisions to an archive depot. p4 archive [-n -h -p -q] -D file[revRange] ... Moves the archives for the specified revisions into the specified depot, which must be an archive depot. The revision's action is changed to 'archive' so that all commands that access revision content will skip the revision. Only revisions that meet the following criteria are archived: - stored in full (+F) or compressed (+C) format - not copied or branched from another revision - not copied or branched to another revision - located in a local depot The storage for the archive depot must be mounted before running this command (unless you are previewing results using the -n flag). The -h flag prevents the head revision of files from being archived. The -n flag displays a preview of the results of the archive operation. The -p flag purges any archives of the specified files in the specified archive depot. On completion, the action for affected revisions is set to 'purge'. The -q flag suppresses messages about skipped revisions. 'p4 archive' requires Perforce 'admin' access. To restore archived revisions, use 'p4 restore'; for details, see 'p4 help restore'. @ @pv@ 0 @db.message@ @en@ 268445791 @ attribute -- Set per-revision attributes on revisions (unsupported) p4 attribute [-e -f -p] -n name [-v value] files... p4 attribute [-e -f -p] -i -n name file Sets a user-managed attribute 'name' to 'value' on opened files. If -v is omitted, the attribute is cleared (if set). To display attributes use 'p4 fstat'. The -e flag indicates that the 'value' is specified in hex. The -f flag sets the attribute on submitted files. The -p flag creates an attribute with a value that is propagated when the file is opened with 'p4 add', 'p4 edit', or 'p4 delete'. The -i flag causes the attribute value to be read from the standard input. Only one file argument is allowed when using this option. Multiple attributes can be set or cleared by specifying multiple '-n name' flags and an equal number of corresponding '-v value' flags (to set) or no '-v' flags (to clear). @ @pv@ 0 @db.message@ @en@ 268445724 @ branches -- Display list of defined branches p4 branches [-u user] [-e nameFilter -m max] Lists all branch specifications defined in the server. Branches takes no arguments. The -u user flag lists branch specs owned by the specified user. The -e nameFilter flag lists branch specs with a name that matches the nameFilter pattern, for example: -e 'svr-dev-rel*' The -m max flag limits output to the specified number of branch specs. @ @pv@ 0 @db.message@ @en@ 268445803 @ browse -- Browse for a list of Zeroconf-registered Perforce servers. p4 browse 'p4 browse' lists all the Perforce servers that have registered with Zeroconf. Requires a 2008.2 or above client and local dynamic libraries and Zeroconf (Avahi or Bonjour) services. @ @pv@ 0 @db.message@ @en@ 268445725 @ change -- Create or edit a changelist description changelist -- synonym for 'change' p4 change [-s] [-f | -u] [changelist#] p4 change -d [-f -s] changelist# p4 change -o [-s] [-f] [changelist#] p4 change -i [-s] [-f | -u] p4 change -t restricted | public [-f | -u] changelist# 'p4 change' creates and edits changelists and their descriptions. With no argument, 'p4 change' creates a new changelist. If a changelist number is specified, 'p4 change' edits an existing pending changelist. In both cases, the changelist specification is placed into a form and the user's editor is invoked. The -d flag deletes a pending changelist, if it has no opened files and no pending fixes associated with it. Use 'p4 opened -a' to report on opened files and 'p4 reopen' to move them to another changelist. Use 'p4 fixes -c changelist#' to report on pending fixes and 'p4 fix -d -c changelist# jobs...' to delete pending fixes. The changelist can be deleted only by the user and client who created it, or by a user with 'admin' privilege using the -f flag. The -o flag writes the changelist specification to the standard output. The user's editor is not invoked. The -i flag reads a changelist specification from the standard input. The user's editor is not invoked. The -f flag forces the update or deletion of other users' pending changelists. -f can also force the deletion of submitted changelists after they have been emptied of files using 'p4 obliterate'. By default, submitted changelists cannot be changed. The -f flag can also force display of the 'Description' field in a restricted changelist. The -f flag requires 'admin' access granted by 'p4 protect'. The -f and -u flags are mutually exclusive. The -u flag can force the update of a submitted change by the owner of the change. Only the Jobs, Type, and Description fields can be changed using the -u flag. The -f and -u flags cannot be used in the same change command. The -s flag extends the list of jobs to include the fix status for each job. On new changelists, the fix status begins as the special status 'ignore', which, if left unchanged simply excludes the job from those being fixed. Otherwise, the fix status, like that applied with 'p4 fix -s', becomes the job's status when the changelist is committed. Note that this option exists to support integration with external defect trackers. The -t flag changes the 'Type' of the change to 'restricted' or 'public' without displaying the change form. This option is useful for running in a trigger or script. The 'Type' field can be used to hide the change or its description from users. Valid values for this field are 'public' (default), and 'restricted'. A shelved or committed change that is 'restricted' is accessible only to users who own the change or have 'list' permission to at least one file in the change. A pending (not shelved) change is accessible to its owner. Public changes are accessible to all users. This setting affects the output of the 'p4 change', 'p4 changes', and 'p4 describe' commands. If a user is not permitted to have access to a restricted change, The 'Description' text is replaced with a 'no permission' message (see 'Type' field). Users with admin permission can override the restriction using the -f flag. @ @pv@ 0 @db.message@ @en@ 268445726 @ changes -- Display list of pending and submitted changelists changelists -- synonym for 'changes' p4 changes [options] [file[revRange] ...] options: -i -t -l -L -f -c client -m max -s status -u user Returns a list of all pending and submitted changelists currently stored in the server. If files are specified, 'p4 changes' lists only changelists that affect those files. If the file specification includes a revision range, 'p4 changes' lists only submitted changelists that affect the specified revisions. See 'p4 help revisions' for details. If files are not specified, 'p4 changes' limits its report according to each change's type ('public' or 'restricted'). If a submitted or shelved change is restricted, the change is not reported unless the user owns the change or has list permission for at least one file in the change. Only the owner of a restricted and pending (not shelved) change is permitted to see it. The -i flag also includes any changelists integrated into the specified files. The -t flag displays the time as well as the date. The -l flag displays the full text of the changelist descriptions. The -L flag displays the changelist descriptions, truncated to 250 characters if longer. The -f flag enables admin users to view restricted changes. The -c client flag displays only submitted by the specified client. The -m max flag limits changes to the 'max' most recent. The -s status flag limits the output to pending, shelved or submitted changelists. The -u user flag displays only changes owned by the specified user. @ @pv@ 0 @db.message@ @en@ 268445727 @ client -- Create or edit a client specification and its view workspace -- synonym for 'client' p4 client [-f -t template] [name] p4 client -d [-f] name p4 client -o [-t template] [name] p4 client -i [-f] Creates a new client workspace specification or edits an existing specification. For new client workspaces, the client name defaults to the $P4CLIENT environment variable if set, or else is derived from the current host name. The specification is put into a temporary file and the editor (configured by the environment variable $P4EDITOR) is invoked. The specification form contains the following fields: Client: The client name (read only). Host: If set, restricts access to the named host. If unset, access is allowed from any host. Owner: The user who created this client. Can be changed. Update: The date that this specification was last modified. Access: The date that this client was last used in any way. Description: A short description of the client (optional). Root: The root directory of the client file workspace (specified in local file system syntax), under which all client files will be placed. If you change this setting, you must physically relocate any files that currently reside there. On Windows client machines, you can specify the root as "null" to enable you to map files to multiple drives. AltRoots: Up to two optional alternate client workspace roots. The first of the main and alternate roots to match the client program's current working directory is used. If none match, the main root is used. 'p4 info' displays the root that is being used. Options: Flags to configure the client behavior. Defaults are marked with *. allwrite Leaves all files writable on the client; noallwrite * by default, only checked-out files are writable. If set, files might be clobbered as a result of ignoring the clobber option (see below). clobber Permits 'p4 sync' to overwrite writable noclobber * files on the client. noclobber is ignored if allwrite is set. compress Compresses data sent between the client nocompress * and server to speed up slow connections. locked Allows only the client owner to use the unlocked * client or change its specification. Prevents the client from being deleted. modtime Causes 'p4 sync' to preserve the file nomodtime * modification time from the submitting client, as with files with +m type modifier. Otherwise modification time is left as when the file was fetched. rmdir Makes 'p4 sync' attempt to delete a client normdir * directory when all files are removed. SubmitOptions: Flags to change submit behaviour. submitunchanged All open files are submitted (default). revertunchanged Files that have content or type changes are submitted. Unchanged files are reverted. leaveunchanged Files that have content or type changes are submitted. Unchanged files are moved to the default changelist. +reopen appended to the submit option flag, causes submitted files to be reopened in the default changelist. Example: submitunchanged+reopen LineEnd: Set line-ending character(s) for client text files. local mode that is native to the client (default). unix linefeed: UNIX style. mac carriage return: Macintosh style. win carriage return-linefeed: Windows style. share hybrid: writes UNIX style but reads UNIX, Mac or Windows style. View: Maps files in the depot to files in your client workspace. Defines the files that you want in your client workspace and specifies where you want them to reside. The default view maps all depot files onto the client. See 'p4 help views' for view syntax. A new view takes effect on the next 'p4 sync'. Note: changing the client root does not actually move the client files; you must relocate them manually. Similarly, changing the 'LineEnd' option does not actually update the client files; you can refresh them with 'p4 sync -f'. The -d flag deletes the specified client workspace, as long as it has no opened files or pending changes. The -f flag forces the delete. The -o flag writes the named client specification to the standard output. The user's editor is not invoked. The -i flag reads a client specification from the standard input. The user's editor is not invoked. The -t flag constructs the client view by using the specified client's view and options as a template, instead of using the existing view or creating a new default view. The -f flag enables users with 'admin' privilege to update locked clients and to set the Last Modified date. @ @pv@ 0 @db.message@ @en@ 268445728 @ clients -- Display list of clients workspaces -- synonym for 'clients' p4 clients [-u user] [-e nameFilter -m max] Lists all client workspaces currently defined in the server. The -u user flag lists client workspaces that are owned by the specified user. The -e nameFilter flag lists workspaces with a name that matches the nameFilter pattern, for example: -e 'svr-dev-rel*' The -m max flag limits output to the specified number of workspaces. @ @pv@ 0 @db.message@ @en@ 268445823 @ copy -- schedule copy of latest revision from one file to another p4 copy [options] fromFile[rev] toFile p4 copy [options] -b branch [-r] [toFile[rev] ...] p4 copy [options] -b branch -s fromFile[rev] [toFile ...] options: -c changelist# -n -v 'p4 copy' schedules the integration and resolve actions that are necessary to make the target files identical to the source files. A branch view, pair of file specifications, or combination of the two can be used to specify the source and target, as with 'p4 integrate' See 'p4 help integrate' for additional information. A single revision specifier can be used, but a revision range cannot, because 'copy' propagates all changes at and before a revision. Like 'p4 integrate', 'p4 copy' opens target files for actions that are appropriate to the desired final state (branch/integrate/delete), but files are opened based on differences between the contents of the source and the head revision of the target. Prior integration history is not considered. Files that exist in the source and target but are different are opened for 'integrate', automatically resolved as 'copies', and synced to the workspace as if a 'p4 resolve -at' had been performed. Files that do not exist (or are deleted) in the source but do exist in the target are opened for 'delete' and removed from the workspace. Files that exist in the source but not the target are opened for 'branch' and synced to the workspace. As with 'p4 resolve -at', a 'copy' action overwrites any changes in the target that have not previously been merged into the source. To merge changes from the source with changes in the target, use the 'p4 integrate' and 'p4 resolve' commands. The target files do not need to be synced to the head revision, but 'p4 copy' exits with a warning if any files are open in the target file path/view. Files that are already open for the correct copy action from an appropriate revision are ignored. The -c changelist# flag opens files in the numbered pending changelist instead of the 'default' changelist. The -n flag displays a preview of the results of the copy. The -v flag speeds up 'p4 copy' by not syncing or modifying any client files. Unlike the 'p4 integrate -v' command, this option affects all files, not just those that are being newly branched @ @pv@ 0 @db.message@ @en@ 268445729 @ counter -- Display, set, or delete a counter p4 counter name p4 counter [-f] name value p4 counter [-f] -d name p4 counter [-i] name The first form displays the value of the specified counter. The second form sets the counter to the specified value. The third form deletes the counter. This option usually has the same effect as setting the counter to 0. The -f flag sets or deletes counters used by Perforce, which are listed by 'p4 help counters'. Important: Never set the 'change' counter to a value that is lower than its current value. The -i flag increments a counter by 1 and returns the new value. This option is used instead of a value argument and can only be used with numeric counters. Counters can be assigned textual values as well as numeric ones, despite the name 'counter'. 'p4 counter' requires 'review' access granted by 'p4 protect'. The -f flag require 'super' access. @ @pv@ 0 @db.message@ @en@ 268445730 @ counters -- Display list of known counters p4 counters Lists the counters in use by the server. The server uses the following counters directly: change Current change number job Current job number journal Current journal number lastCheckpointAction Data about the last complete checkpoint logger Event log index used by 'p4 logger' traits Internal trait lot number used by 'p4 attribute' upgrade Server database upgrade level Other counters can be created by the 'p4 counter' or 'p4 review' commands. Counter names 'minClient', 'minClientMessage', 'monitor', 'security', and 'unicode' are reserved: do not use them as ordinary counters. For general-purpose server configuration, see 'p4 help configure'. @ @pv@ 0 @db.message@ @en@ 268445819 @ cstat -- Dump change/sync status for current client (unsupported) p4 cstat [files...] Lists changes that are needed, had or partially synced in the current client. The output is returned in tagged format, similar to the fstat command. The fields that cstat displays are: change changelist number status 'have', 'need' or 'partial' @ @pv@ 0 @db.message@ @en@ 268445731 @ depot -- Create or edit a depot specification p4 depot name p4 depot -d name p4 depot -o name p4 depot -i Create a new depot specification or edit an existing depot specification. The specification form is put into a temporary file and the editor (configured by the environment variable $P4EDITOR) is invoked. The depot specification contains the following fields: Depot: The name of the depot. This name cannot be the same as any branch, client, or label name. Owner: The user who created this depot. Date: The date that this specification was last modified. Description: A short description of the depot (optional). Type: 'local', 'remote', 'spec', or 'archive'. A 'local' depot (the default) is managed directly by the server and its files reside in the server's root directory. A 'remote' depot refers to files in another Perforce server. A 'spec' depot automatically archives all edited forms (branch, change, client, depot, group, job, jobspec, protect, triggers, typemap, and user) in special, read-only files. The files are named: //depotname/formtype/name[suffix]. Updates to jobs made by the 'p4 change', 'p4 fix', and 'p4 submit' commands are also saved, but other automatic updates such as as access times or opened files (for changes) are not. A server can contain only one 'spec' depot. A 'archive' depot defines a storage location to which obsolete revisions may be relocated. Address: For remote depots, the $P4PORT (connection address) of the remote server. Suffix: For spec depots, the optional suffix to be used for generated paths. The default is '.p4s'. Map: Path translation information, in the form of a file pattern with a single ... in it. For local depots, this path is relative to the server's root directory (Example: depot/...). For remote depots, this path refers to the remote server's namespace (Example: //depot/...). The -d flag deletes the specified depot. If any files reside in the depot, they must be removed with 'p4 obliterate' before deleting the depot. The -o flag writes the depot specification to standard output. The user's editor is not invoked. The -i flag reads a depot specification from standard input. The user's editor is not invoked. @ @pv@ 0 @db.message@ @en@ 268445732 @ depots -- Lists defined depots p4 depots Lists all depots defined in the server. Depots takes no arguments. @ @pv@ 0 @db.message@ @en@ 268445790 @ sizes -- Display information about the size of the files in the depot p4 sizes [-a -S] [-s | -z] [-b blocksize] [-m max] file[revRange] ... For specified file specification, displays depot file name, revision, file count and file size. If you use client syntax for the file specification,the view mapping is used to list the corresponding depot files. The -a flag lists all revisions within the specific range, rather than just the highest revision in the range. The -b option specifies the blocksize in bytes. When this option is specified, each accumulated filesize is rounded up to the nearest blocksize. The -m flag limits sizes to the first 'max' number of files. The -s option calculates the sum of the file sizes for the specified files. The -S option displays size information for shelved files only. With this option, revision specifications are not permitted. The -z option omits lazy copies when calculating the file sizes for the specified files. If there is no file size information for a file revision in the depot metadata, the sizes command returns a size of "". 'p4 verify -u' updates the metadata for all revisions that require it. The sizes command returns a size of "" when there is no file size information for a file revision in the depot metadata. 'p4 verify -u' will update the metadata for all revisions that require it. @ @pv@ 0 @db.message@ @en@ 268445733 @ delete -- Open an existing file for deletion from the depot p4 delete [-c changelist#] [-n -v] file ... Opens a depot file for deletion. If the file is synced in the client workspace, it is removed. If a pending changelist number is specified using with the -c flag, the file is opened for delete in that changelist. Otherwise, it is opened in the default pending changelist. Files that are deleted generally do not appear on the have list. The -n flag displays a preview of the operation without changing any files or metadata. The -v flag enables you to delete files that are not synced to the client workspace.@ @pv@ 0 @db.message@ @en@ 268445734 @ describe -- Display a changelist description p4 describe [-d -s -S -f] changelist# ... Display a changelist description, including the changelist number, user, client, date of submission, textual description, list of affected files and diffs of files updated. Pending changelists are indicated as 'pending' and file diffs are not displayed. For restricted changelists, 'no permission' is displayed if the user is not permitted to view the change (see 'p4 help change'). If a submitted or shelved change is restricted, the description is hidden unless the user is the owner of the change or has list permission for at least one file in the change. To view restricted pending (not shelved) changes, the user must be the owner of the change. The -d passes one or more flags to the built-in diff routine to modify the output: -dn (RCS), -dc[n] (context), -ds (summary), -du[n] (unified), -db (ignore whitespace changes), -dw (ignore whitespace), -dl (ignore line endings). The optional argument to to -dc specifies number of context lines. The -s flag omits the diffs of files that were updated. The -S flag lists files that are shelved for the specified changelist and displays diffs of the files against their previous revision. The -f flag forces display of the descriptions in a restricted change. The -f flag requires 'admin' access, which is granted using 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445735 @ diff -- Display diff of client file with depot file p4 diff [-d -f -m max -s -t] [file[rev] ...] On the client machine, diff a client file against the corresponding revision in the depot. The file is compared only if the file is opened for edit or a revision is provided. See 'p4 help revisions' for details about specifying revisions. If the file specification is omitted, all open files are diffed. This option can be used to view pending changelists. The -d modify the output as follows: -dn (RCS), -dc[n] (context), -ds (summary), -du[n] (unified), -db (ignore whitespace changes), -dw (ignore whitespace), -dl (ignore line endings). The optional argument to -dc specifies number of context lines. The -f flag diffs every file, regardless of whether they are opened or the client has synced the specified revision. This option can be used to verify the contents of the client workspace. The -m max flag limits output to the first 'max' number of files, unless the -s flag is used, in which case it is ignored. The -s options lists the files that satisfy the following criteria: -sa Opened files that differ from the revision in the depot or are missing. -sb Files that have been opened for integrate, resolved, and subsequently modified. -sd Unopened files that are missing on the client. -se Unopened files that differ from the revision in the depot. -sl Every unopened file, along with the status of 'same, 'diff', or 'missing' as compared to its revision in the depot. -sr Opened files that do not differ from the revision in the depot. The -t flag forces 'p4 diff' to diff binary files. If the environment variable $P4DIFF is set, the specified diff program is launched in place of the default Perforce client diff. The -d option can be used to pass arguments to the diff program. Because the -s flag is only implemented internally, any -d option used with the -s is ignored. To configure a diff program for Unicode files, set the environment variable $P4DIFFUNICODE. Specify the file's character set as the first argument to the program. @ @pv@ 0 @db.message@ @en@ 268445736 @ diff2 -- Display diff of two depot files p4 diff2 [-d -q -t -u] file1 file2 p4 diff2 [-d -q -t -u] -b branch [[file1] file2] Diff two depot files on the server. Both files can include a revision specification; by default, the head revisions are diffed. See 'p4 help revisions' for details about specifying file revisions. Wildcards can be used; they must match between file1 and file2. You can use clients or labels in file specifications, preceded with a file path. Example: //...@@mylabel //...@@yourlabel Diff2 precedes each diff with a header line of the following form: ==== file1 (type1) - file2 (type2) ==== summary If either file is displayed as '', it does not exist at the specified revision. The summary status is one of the following: 'identical' means file contents and types are identical, 'types' means file contents are identical but the types are different, and 'content' means file contents are different. The -b flag specifies a branch view to be used to determine the pairs of files to diff. If file specifications are included, they further limit the files and revisions that are diffed. If only one file specification is included, it restricts the right-hand side of the branch view. The -d modify the output of diffs as follows: -dn (RCS) -dc[n] (context) -ds (summary) -du[n] (unified) -db (ignore whitespace changes) -dw (ignore whitespace) -dl (ignore line endings). The optional argument to -dc specifies number of context lines. The -q omits files that have identical content and types and suppresses the actual diff for all files. The -t flag forces 'p4 diff2' to diff binary files. The -u flag uses the GNU diff -u format and displays only files that differ. The file names and dates are in Perforce syntax, but but the output can be used by the patch program. @ @pv@ 0 @db.message@ @en@ 268445737 @ dirs -- List subdirectories of a specified depot directory p4 dirs [-C -D -H] dir[revRange] ... List directories that match the specified file pattern (dir). This command does not support the recursive wildcard (...). Use the * wildcard instead. Perforce does not track directories individually. A path is treated as a directory if there are any undeleted files with that path as a prefix. By default, all directories containing files are listed. If the dir argument includes a revision range, then only directories containing files in the range are listed. For details about specifying file revisions, see 'p4 help revisions'. The -C flag lists only directories that fall within the current client view. The -D includes directories containing only deleted files. The -H flag lists directories containing files synced to the current client workspace. @ @pv@ 0 @db.message@ @en@ 268445800 @ duplicate -- duplicate revisions with integration history (unsupported) p4 duplicate [-n -q] from[revRange] to Duplicate revisions as if they always existed. All aspects of the source revisions are mirrored to the target revisions, including changelist number, date, attributes, and contents. The target revision must not already exist and the target file must not be opened (for any operation) on any client. Integration records are duplicated as well. 'p4 duplicate' followed by a 'p4 obliterate' (of the source revisions) is in effect a deep rename operation, with any source revision in client workspace or labels forgotten. The -n flag displays what would be duplicated without actually copying anything. The -q flag suppresses the warning about target revisions already existing. 'p4 duplicate' requires 'admin' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445738 @ edit -- Open an existing file for edit p4 edit [-c changelist#] [-k -n] [-t filetype] file ... Open an existing file for edit. The server records the fact that the current user has opened the file in the current workspace, and changes the file permission from read-only to read/write. If -c changelist# is included, the file opened in the specified pending changelist. If changelist number is omitted, the file is opened in the 'default' changelist. If -t filetype is specified, the file is assigned that Perforce filetype. Otherwise, the filetype of the previous revision is reused. If a partial filetype is specified, it is combined with the current filetype.For details, see 'p4 help filetypes'. The -n flag previews the operation without changing any files or metadata. The -k flag updates metadata without transferring files to the workspace. This option can be used to tell the server that files in a client workspace are already editable, even if they are not in the client view. Typically this flag is used to correct the Perforce server when it is wrong about the state of files in the client workspace, but incorrect use of this option can result in inaccurate file status information. @ @pv@ 0 @db.message@ @en@ 268445739 @ files -- List files in the depot p4 files [ -a ] [ -A ] [ -m max ] file[revRange] ... List details about specified files: depot file name, revision, file, type, change action and changelist number of the current head revision. If client syntax is used to specify the file argument, the client view mapping is used to determine the corresponding depot files. By default, the head revision is listed. If the file argument specifies a revision, then all files at that revision are listed. If the file argument specifies a revision range, the highest revision in the range is used for each file. For details about specifying revisions, see 'p4 help revisions'. The -a flag displays all revisions within the specific range, rather than just the highest revision in the range. The -A flag displays files in archive depots. The -m flag limits files to the first 'max' number of files. @ @pv@ 0 @db.message@ @en@ 268445740 @ filelog -- List revision history of files p4 filelog [-c changelist# -h -i -l -L -t -m maxRevs -s] file[rev] ... List the revision history of the specified files, from the most recent revision to the first. If the file specification includes a revision, the command lists revisions at or prior to the specified revision. The -c changelist# flag displays files submitted at the specified changelist number. The -i flag includes inherited file history. If a file was created by branching (using 'p4 integrate'), filelog lists the revisions of the file's ancestors up to the branch points that led to the specified revision. File history inherited by renaming (using 'p4 move') is always displayed regardless of whether -i is specified. The -h flag displays file content history instead of file name history. The list includes revisions of other files that were branched or copied (using 'p4 integrate' and 'p4 resolve -at') to the specified revision. Revisions that were replaced by copying or branching are omitted, even if they are part of the history of the specified revision. The -t flag displays the time as well as the date. The -l flag lists the full text of the changelist descriptions. The -L flag lists the full text of the changelist descriptions, truncated to 250 characters if longer. The -m maxRevs displays at most 'maxRevs' revisions per file of the file[rev] argument specified. The -s flag displays a shortened form of filelog that omits non-contributory integrations. @ @pv@ 0 @db.message@ @en@ 268445741 @ fix -- Mark jobs as being fixed by the specified changelist p4 fix [-d] [-s status] -c changelist# jobName ... 'p4 fix' marks each named job as being fixed by the changelist number specified with -c. The changelist can be pending or submitted and the jobs can open or closed (fixed by another changelist). If the changelist has already been submitted and the job is still open, then 'p4 fix' marks the job closed. If the changelist has not been submitted and the job is still open, the job is closed when the changelist is submitted. If the job is already closed, it remains closed. The -d flag deletes the specified fixes. This operation does not otherwise affect the specified changelist or jobs. The -s flag uses the specified status instead of the default defined in the job specification. This status is reported by 'p4 fixes'. The 'p4 fix' and 'p4 change' (of a submitted changelist) and 'p4 submit' (of a pending changelist) commands set the job's status to the fix's status for each job associated with the change. If the fix's status is 'same', the job's status is left unchanged. @ @pv@ 0 @db.message@ @en@ 268445742 @ fixes -- List jobs with fixes and the changelists that fix them p4 fixes [-i -m max -c changelist# -j jobName] [file[revRange] ...] 'p4 fixes' list fixed jobs and the number of the changelist that contains the fix.Fixes are associated with changelists using the 'p4 fix' command or by editing and submitting changelists. The 'p4 fixes' command lists both submitted and pending changelists. By default, 'p4 fixes' lists all fixes. This list can be limited as follows: to list fixes for a specified job, use the -j jobName flag. To list fixes for a specified changelist, use -c changelist#. To list fixes that affect specified files, include the file argument. The file pattern can include wildcards and revision specifiers. For details about revision specifiers, see 'p4 help revisions' The -i flag also includes any fixes made by changelists integrated into the specified files. The -m max flag limits output to the specified number of job fixes. @ @pv@ 0 @db.message@ @en@ 268445744 @ fstat -- Dump file info p4 fstat [-F filter -T fields -m max -r] [-c | -e changelist#] [-Ox -Rx -Sx] file[rev] ... Fstat lists information about files, one line per file. Fstat is intended for use in Perforce API applications, where the output can be accessed as variables, but its output is also suitable for parsing from the client command output in scripts. The fields that fstat displays are: clientFile -- local path (host or Perforce syntax) depotFile -- name in depot movedFile -- name in depot of moved to/from file path -- local path (host syntax) isMapped -- set if mapped client file is synced shelved -- set if file is shelved headAction -- action at head rev, if in depot headChange -- head rev changelist#, if in depot headRev -- head rev #, if in depot headType -- head rev type, if in depot headTime -- head rev changelist time, if in depot headModTime -- head rev mod time, if in depot movedRev -- head rev # of moved file haveRev -- rev had on client, if on client desc -- change description digest -- MD5 digest (fingerprint) fileSize -- file size action -- open action, if opened type -- open type, if opened actionOwner -- user who opened file, if opened change -- open changelist#, if opened resolved -- resolved integration records unresolved -- unresolved integration records otherOpen -- set if someone else has it open otherOpen# -- list of user@@client with file opened otherLock -- set if someone else has it locked otherLock# -- user@@client with file locked otherAction# -- open action, if opened by someone else otherChange# -- changelist, if opened by someone else ourLock -- set if this user/client has it locked resolveAction# -- pending integration record action resolveBaseFile# -- pending integration base file resolveBaseRev# -- pending integration base rev resolveFromFile# -- pending integration from file resolveStartFromRev# -- pending integration from start rev resolveEndFromRev# -- pending integration from end rev The -F flag lists only files satisfying the filter expression. This filter syntax is similar to the one used for 'jobs -e jobview' and is used to evaluate the contents of the fields in the preceding list. Filtering is case-sensitive. Example: -Ol -F "fileSize > 1000000 & headType=text" Note: filtering is not optimized with indexes for performance. The -T fields flag returns only the specified fields. The field names can be specified using a comma- or space-delimited list. Example: -Ol -T "depotFile, fileSize" The -m max flag limits output to the specified number of files. The -r flag sorts the output in reverse order. The -c changelist# flag displays files modified after the specified changelist was submitted. This operation is much faster than using a revision range on the affected files. The -e changelist# flag lists files modified by the specified changelist. When used with the -Ro flag, only pending changes are considered, to ensure that files opened for add are included. This option also displays the change description. The -O options modify the output as follows: -Of output all revisions for the given files (this option suppresses other* and resolve* fields) -Ol output a fileSize and digest field for each revision (this may be expensive to compute) -Op output the local file path in both Perforce syntax (//client/) as 'clientFile' and host form as 'path' -Or output pending integration record information for files opened on the current client -Os exclude client-related data from output The -R option limits output to specific files: -Rc files mapped in the client view -Rh files synced to the client workspace -Rn files opened not at the head revision -Ro files opened -Rr files opened that have been resolved -Rs files shelved (requires -e) -Ru files opened that need resolving The -S option changes the order of output: -St sort by filetype -Sd sort by date -Sr sort by head revision -Sh sort by have revision -Ss sort by filesize For compatibility, the following flags are also supported: -C (-Rc) -H (-Rh) -W (-Ro) -P (-Op) -l (-Ol) -s (-Os). @ @pv@ 0 @db.message@ @en@ 268445818 @ grep -- Print lines matching a pattern p4 grep [options] -e pattern file[revRange]... options: -a -i -n -A -B -C -t -s (-v|-l|-L) (-F|-G) Searches files for lines that match the specified regular expression, which can contain wildcards. The parser used by the Perforce server is based on V8 regexp and might not be compatible with later parsers, but the majority of functionality is available. By default the head revision is searched. If the file argument includes a revision specification, all corresponding revisions are searched. If the file argument includes a revision range, only files in that range are listed, and the highest revision in the range is searched. For details about revision specifiers, see 'p4 help revisions'. The -a flag searches all revisions within the specified range. By default only the highest revision in the range is searched. The -i flag causes the pattern matching to be case-insensitive. By default, matching is case-sensitive. The -n flag displays the matching line number after the file revision number. By default, matches are displayed as revision#: . The -v flag displays files with non-matching lines. The -F flag is used to interpret the pattern as a fixed string. The -G flag is used to interpret the pattern as a regular expression, which is the default behavior. The -L flag displays the name of each selected file from which no output would normally have been displayed. Scanning stops on the first match. The -l flag display the name of each selected file containing matching text. Scanning stops on the first match. The -s flag suppresses error messages that result from abandoning files that have a maximum number of characters in a single line that are greater than 4096. By default, an error is reported when grep abandons such files. The -t flag searches binary files. By default, only text files are searched. The -A flag displays the specified number of lines of trailing context after matching lines. The -B flag displays the specified number of lines of leading context before matching lines. The -C flag displays the specified number of lines of output context. Regular expressions: A regular expression is zero or more branches, separated by `|'. It matches anything that matches one of the branches. A branch is zero or more pieces, concatenated. It matches a match for the first, followed by a match for the second, etc. A piece is an atom possibly followed by `*', `+', or `?'. An atom followed by `*' matches a sequence of 0 or more matches of the atom. An atom followed by `+' matches a sequence of 1 or more matches of the atom. An atom followed by `?' matches a match of the atom, or the null string. An atom is a regular expression in parentheses (matching a match for the regular expression), a range (see below), `.' (matching any single character), `^' (matching the null string at the beginning of the input string), `$' (matching the null string at the end of the input string), a `\' followed by a single character (matching that character), or a single character with no other significance (matching that character). A range is a sequence of characters enclosed in `[]'. It normally matches any single character from the sequence. If the sequence begins with `^', it matches any single character not from the rest of the sequence. If two characters in the sequence are separated by `-', this is shorthand for the full list of ASCII characters between them (e.g. `[0-9]' matches any decimal digit). To include a literal `]' in the sequence, make it the first character (following a possible `^'). To include a literal `-', make it the first or last character. @ @pv@ 0 @db.message@ @en@ 268445745 @ group -- Change members of user group p4 group [-a] name p4 group -d [-a] name p4 group -o name p4 group -i [-a] Create a group or modify the membership of an existing group. A group can contain users and other groups. The group specification is put into a temporary file and the editor (configured by the environment variable $P4EDITOR) is invoked. A group exists when it has any users or other groups in it, and ceases to exist if all users and groups in it are removed. Each group has MaxResults, MaxScanRows, and MaxLockTime fields, which limit the resources committed to operations performed by members of the group. For these fields, 'unlimited' or 'unset' means no limit for that group. An individual user's limit is the highest of any group with a limit to which he belongs, unlimited if any of his groups has 'unlimited' for that field, or unlimited if he belongs to no group with a limit. See 'p4 help maxresults' for more information on MaxResults, MaxScanRows and MaxLockTime. Each group also has a Timeout field, which specifies how long (in seconds) a 'p4 login' ticket remains valid. A value of 'unset' or 'unlimited' is equivalent to no timeout. An individual's timeout is the highest of any group with a limit to which he belongs, unlimited if any of his groups has 'unlimited' for the timeout value, or unlimited if he belongs to no group with a limit. See 'p4 help login' for more information. Each group has a PasswordTimeout field, which determines how long a password remains valid for members of the group. The -d flag deletes a group. The -o flag writes the group specification to standard output. The user's editor is not invoked. The -i flag reads a group specification from standard input. The user's editor is not invoked. The new group specification replaces the previous one. The -a flag enables a user without 'super' access to modify the group if that user is an 'owner' of that group. Group owners are specified in the 'Owners' field of the group spec. All commands that require access granted by 'p4 protect' consider a user's groups when calculating access levels. 'p4 group' requires 'super' access granted by 'p4 protect' unless invoked with the '-a' flag by a qualified user. @ @pv@ 0 @db.message@ @en@ 268445746 @ groups -- List groups (of users) p4 groups [-m max] [[[-i] user | group] | [-v [group]]] List all user defined in the server. If a user argument is specified, only groups containing that user are displayed. If a group argument is specified, only groups containing the group are displayed. The -i flag also displays groups that the user or group belongs to indirectly by means of membership in subgroups. The -m max flag limits output to the specified number of groups. The -v flag displays the MaxResults, MaxScanRows, MaxLockTime, and Timeout values for the specified group. @ @pv@ 0 @db.message@ @en@ 268445747 @ have -- List the revisions most recently synced to the current workspace p4 have [file ...] List revision numbers of the currently-synced files. If file name is omitted, list all files synced to this client workspace. The format is: depot-file#revision - client-file @ @pv@ 0 @db.message@ @en@ 268445748 @ help -- Print help message p4 help [command ...] Print usage details about the specified command. If the command name is omitted, print a general help message about Perforce and list the available client commands. @ @pv@ 0 @db.message@ @en@ 268445792 @ index -- Add words to the jobs index (unsupported) p4 index [-a attrib] [-d] name Index is an interface to the search engine used to search jobs. It reads its standard input for text, breaks the text into words, and adds those words to the search engine's index with the key 'name' and the optional attribute 'attrib'. (Job fields are entered with the name of the job as the name and the field name as the attribute.) If -a attrib is specified, that attribute number is used instead of 0. The -d option deletes entries from the index. See also 'p4 help search'. @ @pv@ 0 @db.message@ @en@ 268445749 @ info -- Display client/server information p4 info [-s] Info lists information about the current client (user name, client name, applicable client root, client current directory, and the client IP address) and some server information (server IP address, server root, date, uptime, version and license data). The -s option produces 'short' output that omits any information that requires a database lookup such as the client root). @ @pv@ 0 @db.message@ @en@ 268445750 @ integrate -- schedule integrations from one file to another p4 integrate [options] fromFile[revRange] toFile p4 integrate [options] -b branch [toFile[revRange] ...] p4 integrate [options] -b branch -s fromFile[revRange] [toFile ...] options: -c changelist# -d -D -f -h -i -o -n -r -t -v 'p4 integrate' prepares the propagation of change from source files to target files. It opens the target files in the client workspace for integrate.'p4 resolve' then merges content from the source files into the opened target files, and 'p4 submit' commits the opened files to the depot. Integrations can be abandoned with 'p4 revert'. When 'p4 integrate' opens a target file in the client workspace, it chooses an appropriate action: 'branch' for new files, 'integrate' when the source file has changed, and 'delete' when the source file was deleted. Open target files are left read-only in the client workspace. 'p4 edit' can downgrade a 'branch' to an 'add' or an 'integrate' to an 'edit', making the file read-write. 'p4 integrate' maintains the history of integrations between files. The history prevents duplicate integrations and minimizes file merges by telling 'p4 resolve' what to use as the merge base: generally, the highest revision that was already integrated. Integration history also prevents integrating back a pure, integration-only change, which results from 'p4 resolve' without manually editing the file. The search for integration history includes integrations performed indirectly through intermediate file branches. The commands 'p4 integrated' and 'p4 filelog' display integration history. Source and target files can be specified on the command line or as a branch view using the -b flag. A branch view can have many mappings, while the command line can only have one. If the file specification is omitted, the entire branch view is examined for needed integrations. If a file specification is specified with a branch view, the integration is limited to the specified target files. In both cases, the integration is also limited to target files that are in the client view. If the revision specification is omitted, all revisions of the source file are considered for integration. If a single revision is specified, revisions up to the given revision are included. If a range of revisions is specified, that range integrated. Note: The revision specification refers to the fromFile parameter, but is specified with the toFile parameter. For details about revision specifiers, see 'p4 help revisions'. The -f flag forces integrate to ignore previous integration history. By default, integrate skips file revisions that were already integrated. Note: if revRange is omitted, the -f flag requires 'p4 resolve' to perform merges without a common base. To avoid this situation, use -f only to force integration of specific changes. If -c changelist# is specified, the files are opened in the designated numbered pending changelist instead of the 'default' changelist. The -d and -Dx flags enable integrations around deleted revisions. Normally 'p4 integrate' avoids mixing outstanding edits with a deleted file. To enable all the options, specify -d. To specify individual options, use the following flags: -Dt If the target file has been deleted and the source file has changed, re-branch the source file on top of the target file. -Ds If the source file has been deleted and the target file has changed, delete the target file. -Di If the source file has been deleted and re-added, attempt to integrate all outstanding revisions of the file, including revisions prior to the delete. By default, 'p4 integrate' only considers revisions since the last add. The -h flag leaves the target files at the revision currently synced to the client (the '#have' revision). By default, target files are automatically synced to the head revision by 'p4 integrate'. [Prior to 2002.1, files were not automatically synced by 'p4 integrate'.] The -i flag enables integration between files that have no integration history. By default, 'p4 integrate' does not integrate changes if there is no prior integration history between the source and target, because it cannot identify the base for its merges. The -i flag enables baseless merges using the earliest revision as the base. The -o flag displays the base file name and revision that will be used in subsequent resolves if a resolve is needed. The -n flag displays a preview of required integrations. The -r flag reverses the mappings in the branch view, with the target files and source files exchanging place. The -b branch flag is required. The -s fromFile[revRange] flag causes the branch view to work bidirectionally, where the scope of the command is limited to integrations in which 'from' files match fromFile[revRange]. If any toFiles are specified, the scope is further limited to integrations with matching 'to' files. If the -s fromFile[revRange] flag is used -r has no effect, and any revisions specified with the toFile parameter are ignored. [The -s flag is provided for use by Perforce graphical client programs.] The -t flag propagates the source file's filetype to the target file (By default, the target file retains its filetype.) Newly-branched files always inherit the source file's filetype. To change the filetype before submitting, use the 'p4 reopen' command. The -v flag speeds integration by not syncing newly-branched files to the client. The files can be synced after they are submitted. [In release 97.2 and earlier, newly-branched files were synced by default.] Note: The 'p4 integrate -b branch toFile[revRange]' syntax is provided for backwards compatibility, but might be confusing because it mixes the target file with the source revisions. @ @pv@ 0 @db.message@ @en@ 268445751 @ integrated -- List integrations that have been submitted p4 integrated [-r] [-b branch] [file ...] The p4 integrated command lists integrations that have been submitted. To list unresolved integrations, use 'p4 resolve -n'. To list resolved but unsubmitted integrations, use 'p4 resolved'. If the -b branch flag is specified, only files integrated from the source to target files in the branch view are listed. Qualified files are listed, even if they were integrated without using the branch view. The -r flag reverses the mappings in the branch view, swapping the target files and source files. The -b branch flag is required. @ @pv@ 0 @db.message@ @en@ 268445752 @ job -- Create or edit a job (defect) specification p4 job [-f] [jobName] p4 job -d jobName p4 job -o [jobName] p4 job -i [-f] The 'p4 job' command creates and edits job specifications using an ASCII form. A job is a defect, enhancement, or other unit of intended work.The 'p4 fix' command associates changelists with jobs. With no arguments, 'p4 job' creates an empty job specification and invokes the user's editor. When the specification is saved, a job name of the form jobNNNNNN is assigned. If the jobName parameter is specified on the command line, the job is created or opened for editing. As jobs are entered or updated, all fields are indexed for searching Text fields are broken into individual alphanumeric words (punctuation and whitespace are ignored) and each word is case-folded and entered into the word index. Date fields are converted to an internal representation (seconds since 1970/01/01 00:00:00) and entered into the date index. The fields that compose a job are defined by the 'p4 jobspec' command. Perforce provides a default job specification that you can edit. The -d flag deletes the specified job. You cannot delete a job if it has pending or submitted fixes associated with it. The -o flag writes the job specification to the standard output. The user's editor is not invoked. The -i flag reads a job specification from the standard input. The user's editor is not invoked. The -f flag enables you set fields that are read-only by default. The -f flag requires 'admin' access, which is granted using the 'p4 protect' command. @ @pv@ 0 @db.message@ @en@ 268445793 @ interchanges -- report changes not yet integrated (unsupported) p4 interchanges [options] fromFile[revRange] toFile p4 interchanges [options] -b branch [toFile[revRange] ...] p4 interchanges [options] -b branch -s fromFile[revRange] [toFile ...] options: -C changelist# -f -l -r -t This command lists changes that have not been integrated from a set of source files to a set of target files. The -f option lists the individual files that require integration. For partially-integrated changelists, files might be listed even if they have been integrated individually. The -l flag includes the full text of the changelist descriptions. The -t flag displays the time as well as the date. The -C changelist#, -b branch, -r, and -s flags work as they do with 'p4 integrate' (see 'p4 help undoc' for -C changelist#). @ @pv@ 0 @db.message@ @en@ 268445753 @ jobs -- Display list of jobs p4 jobs [-e jobview -i -l -m max -r] [file[revRange] ...] p4 jobs -R Lists jobs in the server. If a file specification is included, fixes for submitted changelists affecting the specified files are listed. The file specification can include wildcards and a revision range. See 'p4 help revisions' for details about specifying revisions. The -e flag lists jobs matching the expression specified in the jobview parameter. For a description of jobview syntax, see 'p4 help jobview'. The -i flag includes any fixes made by changelists integrated into the specified files. The -l flag produces long output with the full text of the job descriptions. The -m max flag limits the output to the first 'max' jobs, ordered by their job name. The -r flag sorts the jobs in reverse order (by job name). The -R flag rebuilds the jobs table and reindexes each job, which is necessary after upgrading to 98.2. 'p4 jobs -R' requires 'super' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445754 @ jobspec -- Edit the job template p4 jobspec p4 jobspec -o p4 jobspec -i Jobspec edits the template that specifies the format of jobs. This format is used by 'p4 job' when jobs are entered or updated, and by 'p4 jobs' and 'p4 describe' when jobs are displayed. Jobspec brings up a form with the following fields: Fields: A list of the fields maintained for each job, one line per field. Each line has five words: code, name, data-type, len, and field-type. 'code' is a unique integer identifier for storing the data of the field. Job codes must be between 101 and 199. 'name' is the name of the field for the job. 'data-type' indicates the format of the field: word: a single word (any value) date: a date/time field select: one of a set of words line: a one-liner text: a block of text bulk: text not indexed for 'p4 jobs -e' 'len' is the recommended character length of a display box for the field. If 0, a text box is assumed. 'field-type' indicates how to handle the setting of the field: optional: no default, and not required to be present default: default provided, still not required required: default provided, value must be present once: set once to the default and never changed always: always set to the default when saving the form, adding or deleting fixes with 'p4 fix' or 'p4 changelist', or submitting a change associated with the job with 'p4 submit'. Values: A list of 'select' fields and the values that the fields can have. Each line has two words: the field name and the values list, with individual values separated by '/' (no spaces). Presets: A list of fields and their default values, for fields whose 'setting' flag is other than 'optional'. Each line has two words: the field name and the default value. If the value has spaces, it must be enclosed in double quotes. The following special defaults are recognized: $user: the user entering the job $now: the current date $blank: the words '' The Preset for the job status field (code 102) has a special syntax for providing a default fix status for 'p4 fix' and 'p4 change' along with the default status for new jobs: jobStatus,fix/fixStatus Otherwise the fixStatus is hardwired to 'closed'. Comments: text to be included at the top of each job specification, to help the user fill out the form. Each line must begin with the comment character '#'. The following field codes are reserved: code 101, required: the job name code 102, optional: the job status code 103, optional: the user who created the job code 104, optional: the date the job was created code 105, optional: the description If there is a job status field (102), 'p4 fix' and 'p4 change' (of a submitted changelist) and 'p4 submit' (of a pending changelist) will set the job's status to the fix's status for each job associated with the change. If the fix's status is the special value 'same', the job's status is left unchanged. Fields 102-105 are used by 'p4 describe' and 'p4 jobs' to display a job summary. Missing fields are omitted from the summary. If field 105 is present, it is treated as a description, which is used by 'p4 change' and 'p4 submit' to annotate the list of jobs to be fixed by the changelist being created. If you change the jobspec after jobs have been created, note the following limitations: Data is stored according to its code. Fields can be renamed by keeping the same code. Removing a code can cause the associated data stored for the code to become abandoned. Changing the definition of a code (for example, from 'text' to 'word') can require users to correct jobs for the new format during editing. The -o flag writes the job template to the standard output. The user's editor is not invoked. The -i flag reads a job template from the standard input. The user's editor is not invoked. 'p4 jobspec' requires 'admin' access, which is granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445755 @ label -- Create or edit a label specification p4 label [-f -t template] name p4 label -d [-f] name p4 label -o [-t template] name p4 label -i [-f] Create or edit a label. The name parameter is required. The specification form is put into a temporary file and the editor (configured by the environment variable $P4EDITOR) is invoked. The label specification form contains the following fields: Label: The label name (read only.) Owner: The user who created this label. Can be changed. Update: The date that this specification was last modified. Access: The date of the last 'labelsync' or use of '@@label' referencing this label. Description: A short description of the label (optional). Options: Flags to change the label behavior. locked Prevents users other than the label owner from changing the specification. Prevents the label from being deleted. Prohibits 'p4 labelsync'. Revision: An optional revision specification for an automatic label. Enclose in double quotes if it contains the # (form comment) character. View: A mapping that selects files from the depot. The default view selects all depot files. Only the left side of the mapping is used for labels. A label is a named collection of revisions. A label is either automatic or static. An automatic label refers to the revisions given in the View: and Revision: fields. A static label refers to the revisions that are associated with the label using the 'p4 tag' or 'p4 labelsync' commands. A static label cannot have a Revison: field. See 'p4 help revisions' for information on using labels as revision specifiers. Flag -d deletes the specified label. You cannot delete a locked label. The -f flag forces the delete. The -o flag writes the label specification to standard output. The user's editor is not invoked. The -i flag reads a label specification from standard input. The user's editor is not invoked. The -t flag copies the view and options from the template label to the new label. The -f flag forces the deletion of a label. By default, locked labels can only be deleted by their owner. The -f flag also permits the Last Modified date to be set. The -f flag requires 'admin' access, which is granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445756 @ labels -- Display list of defined labels p4 labels [-t] [-u user] [-e nameFilter -m max] [file[revrange]] Lists labels defined in the server. If files are specified, 'p4 labels' lists the labels that contain those files. If you include a file specification, automatic lablels are omitted from the list. If the file specification includes a revision range, 'p4 labels' lists labels that contain the specified revisions. See 'p4 help revisions for details about specifying revisions. The -t flag displays the time as well as the date. The -u user flag lists labels owned by the specified user. The -e nameFilter flag lists labels with names that match the specified filter pattern. Example: -e 'svr-dev-rel*' The -m max flag limits output to the first 'max' number of labels. @ @pv@ 0 @db.message@ @en@ 268445757 @ labelsync -- Apply the label to the contents of the client workspace p4 labelsync [-a -d -n -q] -l label [file[revRange] ...] Labelsync causes the specified label to reflect the current contents of the client. It records the revision of each file currently synced. The label's name can subsequently be used in a revision specification as @@label to refer to the revision of a file as stored in the label. Without a file argument, labelsync causes the label to reflect the contents of the whole client, by adding, deleting, and updating the label. If a file is specified, labelsync updates the specified file. If the file argument includes a revision specification, that revision is used instead of the revision synced by the client. If the specified revision is a deleted revision, the label includes that deleted revision. See 'p4 help revisions' for details about specifying revisions. If the file argument includes a revision range specification, only files selected by the revision range are updated, and the highest revision in the range is used. The -a flag adds the specified file to the label. The -d deletes the specified file from the label, regardless of revision. The -n flag previews the operation without altering the label. Only the owner of a label can run labelsync on that label. A label that has its Options: field set to 'locked' cannot be updated. The -q flag suppresses normal output messages. Messages regarding errors or exceptional conditions are displayed. @ @pv@ 0 @db.message@ @en@ 268445797 @ license -- Update or display the license file p4 license -o p4 license -i Update the Perforce license file. This command requires a valid license file in the Perforce root directory. Typically this command lets an administrator add extra licensed users to the Perforce server without having to shut the server down and copy the license file to the server root. Most new license files obtained from Perforce can be installed with this command, unless the server's IP address has changed. In that case, stop the server, copy the new license file to the root, and restart the server. The -o flag writes the license file to the standard output. The -i flag reads a license file from the standard input. This command requires 'super' access, which is granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445758 @ lock -- Lock an open file to prevent it from being submitted p4 lock [-c changelist#] [file ...] The specified files are locked in the depot, preventing any user other than the current user on the current client from submitting changes to the files. If a file is already locked, the lock request is rejected. If no file names are specified, all files in the specified changelist are locked. If changelist number is omitted, files in the default changelist are locked. @ @pv@ 0 @db.message@ @en@ 268445759 @ logger -- Report changed jobs and changelists p4 logger [-c sequence#] [-t counter] Dumps the event log, which notes updates to changes and jobs, for use with defect tracking integration. The event log is enabled by setting the counter 'logger' to 0 using the 'p4 counter' command. Each event is assigned a sequence number. The presence of an entry in the log doesn't guarantee that the named entity has changed. If a sequence# is specified using the -c flag, only events after that number are listed. If a counter is given using the -t flag, only events after the number of that counter are listed. If both are specified, the counter is updated to the sequence number and nothing is output. If the update brings the counter to the highest sequence number in the log, the log is cleared. Important: 'p4 logger' is not intended for end users. It is used by P4DTG to help propagate information to an external defect tracking system. 'p4 logger -c' requires 'review' access, which is granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445785 @ login -- Log in to Perforce by obtaining a session ticket p4 login [-a -p] [user] p4 login [-s] The login command enables a user to access Perforce until the session expires or the user logs out. When a user logs in to Perforce, they are prompted for a password If they enter the correct password, they are issued a ticket. The ticket expires when the default timeout value has been reached and is valid only for the host machine where the 'login' command was executed (see below for exception). The ticket can be used anywhere that a password can be used. Example: p4 -P changes -m1 The -a flag causes the server to issue a ticket that is valid on all host machines. The -p flag displays the ticket, but does not store it on the client machine. The -s flag displays the status of the current ticket (if there is one). Requesting a login of someone other than the current user requires 'super' access, which is granted by 'p4 protect'. In this case, 'p4 login' does not prompt for the password. @ @pv@ 0 @db.message@ @en@ 268445786 @ logout -- Log out from Perforce by removing or invalidating a ticket. p4 logout [-a] The logout command removes the ticket on the client. To resume using Perforce, the user must log in again. The -a flag invalidates the ticket on the server, which will log out all users of the ticket. @ @pv@ 0 @db.message@ @en@ 268445794 @ merge3 -- three-way file merge (unsupported) p4 merge3 [-db -dw -r -t -v] base leg1 leg2 Performs a three-way merge of the specified files and writes the results to standard output. This command is implemented on the client and requires file names to be specified using client syntax. This command is used to support Perforce's graphical merge tools. The -db, -dw, -t, and -v flags are the same as in 'p4 resolve'. -r formats the output from a special one to one more like 'p4 resolve'. @ @pv@ 0 @db.message@ @en@ 268445784 @ monitor -- Display Perforce process information p4 monitor show [-a -l -e] p4 monitor terminate [id] p4 monitor clear [id | all] Monitor displays running p4 processes. Monitor tracks the Perforce processes using a dedicated table. This table is constantly updated, so there is a potential minor impact on server performance. To enable this command,set the monitor counter as follows: To monitor active commands, set the counter to 1. To monitor idle connections and active, set the counter to 2. To start monitoring, restart the server after setting the counter. 'p4 monitor show' displays current process information. For each process, a single line of output lists the process ID, status owner, and command. The following flags require 'super' access: The -a flag includes the command args. The -e flag includes the command environment. For each process, client application (if known), host address and client name are displayed. The -l flag displays long output, including the full username and argument list. 'p4 monitor terminate [id]' marks the specified command for termination. This command requires 'super' access. 'p4 monitor clear [id|all]' removes the specified process record from the monitor table. All of the records are removed if the option 'all' is supplied instead of an ID. This option might be required if for some reason commands are ending prematurely. This command requires 'super' access. @ @pv@ 0 @db.message@ @en@ 268445804 @ move -- move file(s) from one location to another p4 move [-c changelist#] [-f -n -k] [-t filetype] fromFile toFile Move takes an already opened file and moves it from one client location to another, reopening it as a pending depot move. When the file is submitted with 'p4 submit', its depot file is moved accordingly. Wildcards in fromFile and toFile must match. The fromFile must be a file open for add or edit. 'p4 opened' lists pending moves. 'p4 diff' can compare a moved client file with its depot original, 'p4 sync' can schedule an update of a moved file, and 'p4 resolve' can resolve the update. A client file can be moved many times before it is submitted. Moving a file back to its original location will undo a pending move, leaving unsubmitted content intact. Using 'p4 revert' undoes the move and reverts the unsubmitted content. If -c changelist# is specified, the file is reopened in the specified pending changelist as well as being moved. The -f flag forces a move to an existing target file. The file must be synced and not opened. The originating source file will no longer be synced to the client. If -t filetype is specified, the file is assigned that filetype. If the filetype is a partial filetype, the partial filetype is combined with the current filetype. See 'p4 help filetypes'. The -n flag previews the operation without moving files. The -k flag performs the rename on the server without modifying client files. Use with caution, as an incorrect move can cause discrepancies between the state of the client and the corresponding server metadata. The 'move' command requires a release 2009.1 or newer client. The '-f' flag requires a 2010.1 client. For pre-2009.1 clients, see instructions in 'p4 help rename'. @ @pv@ 0 @db.message@ @en@ 268445760 @ obliterate -- Remove files and their history from the depot p4 obliterate [-y] file[revRange] ... Obliterate permanently removes files and their history from the server. (See 'p4 delete' for the non-destructive way to delete a file.) Obliterate retrieves the disk space used by the obliterated files in the archive and clears the files from the metadata that is maintained by the server. Files in client workspaces are not physically affected, but they are no longer under Perforce control. Obliterate is aware of lazy copies made when 'p4 integrate' creates a branch, and does not remove copies that are still in use. Because of this, obliterating files does not guarantee that the corresponding files in the archive will be removed. If the file argument has a revision, the specified revision is obliterated. If the file argument has a revision range, the revisions in that range are obliterated. See 'p4 help revisions' for help. By default, obliterate displays a preview of the results. To execute the operation, you must specify the -y flag. 'p4 obliterate' requires 'admin' access, which is granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445761 @ opened -- List open files and display file status p4 opened [-a -c changelist# -C client -u user -m max] [file ...] Lists files currently opened in pending changelists, or, for specified files, show whether they are currently opened or locked. If the file specification is omitted, all files open in the current client workspace are listed. The -a flag lists opened files in all clients. By default, only files opened by the current client are listed. The -c changelist# flag lists files opened in the specified changelist#. The -C client flag lists files open in the specified client workspace. The -u user flag lists files opened by the specified user. The -m max flag limits output to the first 'max' number of files. @ @pv@ 0 @db.message@ @en@ 268445762 @ passwd -- Set the user's password on the server (and Windows client) p4 passwd [-O oldPassword -P newPassword] [user] 'p4 passwd' sets the user's password on the server. After a password is set for a user, the same password must be set on the client in the environment variable $P4PASSWD to enable the user to use all Perforce client applications on that machine. (On Windows, you can use 'p4 passwd' to configure the password in the environment.) 'p4 passwd' prompts for both the old password and the new password with character echoing turned off. To delete the password, set it to an empty string. The -O flag provides the old password, avoiding prompting. The -P flag provides the new password, avoiding prompting. If you are using ticket-based authentication, changing your password automatically invalidates all of your tickets and logs you out. Setting the password of someone other than the current user requires 'super' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445763 @ print -- Write a depot file to standard output p4 print [-a -o localFile -q] file[revRange] ... Retrieve the contents of a depot file to the client's standard output. The file is not synced. If file is specified using client syntax, Perforce uses the client view to determine the corresponding depot file. By default, the head revision is printed. If the file argument includes a revision, the specified revision is printed. If the file argument has a revision range, then only files selected by that revision range are printed, and the highest revision in the range is printed. For details about revision specifiers, see 'p4 help revisions'. The -a flag prints all revisions within the specified range, rather than just the highest revision in the range. The -o localFile flag redirects the output to the specified file on the client filesystem. The -q flag suppresses the initial line that displays the file name and revision. @ @pv@ 0 @db.message@ @en@ 268445764 @ protect -- Modify protections in the server namespace p4 protect p4 protect -o p4 protect -i 'p4 protect' edits the protections table in a text form. Each line in the table contains a protection mode, a group/user indicator, the group/user name, client host ID and a depot file path pattern. Users receive the highest privilege that is granted on any line. Note: remote depot are accessed using the pseudo-user 'remote'. To control access from other servers that define your server as a remote server, grant appropriate permissions to the 'remote' user. Mode: The permission level or right being granted or denied. Each permission level includes all the permissions above it, except for 'review'. Each permission only includes the specific right and no lesser rights. This approach enables you to deny individual rights without having to re-grant lesser rights. Modes prefixed by '=' are rights. All other modes are permission levels. Valid modes are: list - users can see names but not contents of files; users can see all non-file related metadata (clients, users, changelists, jobs, etc.) read - users can sync, diff, and print files open - users can open files (add, edit. delete, integrate) write - users can submit open files admin - permits those administrative commands and command options that don't affect the server's security. super - access to all commands and command options. review - permits access to the 'p4 review' command; implies read access =read - if this right is denied, users can't sync, diff, or print files =branch - if this right is denied, users are not permitted to use files as a source for 'p4 integrate' =open = if this right is denied, users cannot open files (add, edit, delete, integrate) =write = if this right is denied, users cannot submit open files Group/User indicator: specifies the grantee is a group or user. Name: A Perforce group or user name; can include wildcards. Host: The IP address of a client host; can include wildcards. Path: The part of the depot to which access is being granted or denied. To deny access to a depot path, preface the path with a "-" character. These exclusionary mappings apply to all access levels, even if only one access level is specified in the first field. The -o flag writes the protection table to the standard output. The user's editor is not invoked. The -i flag reads the protection table from the standard input. The user's editor is not invoked. After protections are defined, 'p4 protect' requires 'super' access. @ @pv@ 0 @db.message@ @en@ 268445789 @ protects -- Display protections defined for a specified user and path p4 protects [-a | -g group | -u user] [-h host -m] [file ...] 'p4 protects' displays the lines from the protections table that apply to the current user. The protections table is managed using the 'p4 protect' command. If the -a flag is specified, protection lines for all users are displayed. If the -g group flag or -u user flag is specified, protection lines for that group or user are displayed. If the -h host flag is specified, the protection lines that apply to the specified host (IP address) are displayed. If the -m flag is given, a single word summary of the maximum access level is reported. Note that this summary does not take exclusions into account. If the file argument is specified, protection lines that apply to the specified files are displayed. The -a/-g/-u flags require 'super' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445765 @ rename -- How to rename files using pre-2009.1 clients In release 2009.1 and higher, you can use 'p4 move' to move or rename files. Perforce clients prior to release 2009.1 do not support 'p4 move'. However, files in older clients can be renamed by branching one file to another and deleting the original file. For example: p4 integrate fromFile toFile p4 delete fromFile p4 submit For further information, see the help for the individual commands. Note: Files renamed in this way are treated as branched files rather than moved files in subsequent operations. @ @pv@ 0 @db.message@ @en@ 268445766 @ reopen -- Change the filetype of an open file or move it to another changelist p4 reopen [-c changelist#] [-t filetype] file ... Reopen an open file for the current user in order to move it to a different changelist or change its filetype. The target changelist must exist; you cannot create a changelist by reopening a file. To move a file to the default changelist, use 'p4 reopen -c default'. If -t filetype is specified, the file is assigned that filetype. If a partial filetype is specified, it is combined with the current filetype. For details, see 'p4 help filetypes'. @ @pv@ 0 @db.message@ @en@ 268445767 @ resolve -- Merge open files with other revisions or files p4 resolve [-af -am -as -at -ay -d -f -n -o -t -v] [file ...] 'p4 resolve' merges the content of source files into target files that are open in the client workspace. 'p4 resolve' only handles merges scheduled implicitly by 'p4 sync' or 'p4 submit' of a file opened at a revision other than the head or explicitly by 'p4 integrate'. Merges must be performed before the file can be submitted. If the file argument is omitted, all files needing merging are resolved. The merge process is a classic three-way merge. The participating files are referred to as follows: yours The target file open in the client workspace theirs The source file being merged from the depot base The common ancestor; the highest revision of the source file not already merged into the target. For each file, 'p4 resolve' places a merge candidate into a temporary file in the client workspace and displays a summary line with the total number of sections of text changed from the base: yours change is only in your open revision theirs change is only in the source revision both same text added or changed in both conflicts conflicting changes between the yours and theirs If there are any conflicts, the merge candidate file contains conflict markers bracketing the alternative texts. You must edit the file to resolve the conflicts and remove the markers. 'p4 resolve' distinguishes among four potential merge results: entirely yours, entirely theirs, automated merge, or manually edited merge. All but the last result in a pure merge: one that never needs integrating back to the source file. 'p4 resolve' includes a suggested merge result in []'s on its prompt line. After displaying the summary line, 'p4 resolve' prompts you for an action: Accept: at Keep only changes to their file. ay Keep only changes to your file. * am Keep merged file. * ae Keep merged and edited file. * a Keep autoselected file. Diff: * dt See their changes alone. * dy See your changes alone. * dm See merged changes. d Diff your file against merged file. Edit: et Edit their file (read only). ey Edit your file (read/write). * e Edit merged file (read/write). Misc: * m Run '$P4MERGE base theirs yours merged'. (Runs '$P4MERGEUNICODE charset base theirs yours merged' if set and the file is a unicode file.) s Skip this file. h Print this help message. ^C Quit the resolve operation. Options marked (*) appear only for textfiles. The 'merge' option enables you to invoke your own integration and conflict resolution utility (configured using the $P4MERGE environment variable). This utility must replace the existing merged file with a new one. The -am flag puts 'p4 resolve' into automatic mode: if there are conflicts, the file is skipped; if there are no conflicts and yours hasn't changed it accepts theirs; if theirs hasn't changed it accepts yours; if both yours and theirs have changed it accepts the merge. Files that have no base for merging (such as binary files) are skipped. The -af flag forces 'p4 resolve' in automatic mode to accept the merged file even if there are conflicts. The -as flag performs a 'safe' automatic resolve, accepting only files that have either your changes or their changes, but not both. Files with changes to both yours and theirs are skipped. The -at and -ay flags perform an automatic resolve that skips the merging. Instead it automatically accepts their (-at) or your (-ay) version of the file. The -at flag should be used with care, as it overwrites any changes made to the file in the client workspace. The -d flags can be used to control handling of whitespace and line endings when merging files. The -db flag ignores whitespace changes, the -dw flag ignores whitespace altogether, and the -dl flag ignores line endings when merging files. The flags are also passed to the diff options in the 'p4 resolve' dialog. Additional -d flags that modify the diff output but do not modify merge behavior include -dn (RCS), -dc (context), -ds (summary), and -du (unified). Note that 'p4 resolve' uses text from the client file if the files differ only in whitespace. The -f flag enables previously resolved files to be resolved again. By default, after files have been resolved, 'p4 resolve' does not display them again. The -n flag previews the operation without altering files. The -o flag displays the base file name and revision to be used during the the merge. The -t flag forces 'p4 resolve' to attempt a textual merge, even for files with non-text (binary) types. The -v flag causes 'p4 resolve' to insert markers for all changes, not conflicts. The markers must be deleted before the merged file can be accepted. @ @pv@ 0 @db.message@ @en@ 268445768 @ resolved -- Show files that have been merged but not submitted p4 resolved [-o] [file ...] Resolved lists integrations that have been resolved but not yet submitted. To see unresolved integrations, use 'p4 resolve -n'. To see already submitted integrations, use 'p4 integrated'. If a depot file path is specified, the output lists resolves for 'theirs' files that match the specified path. If a client file path is specified, the output lists resolves for 'yours' files that match the specified path. The -o flag reports the revision used as the base during the resolve. @ @pv@ 0 @db.message@ @en@ 268445822 @ restore -- Restore revisions from an archive depot. p4 restore [-n] -D file[revRange] ... Moves previously archived revisions from the specified archive depot back to their original locations. The revision's action is set to its original value (add/edit/etc.). The -n flag displays a preview of the operation. The storage for the archive depot must be mounted before running this command (except for preview). 'p4 restore' requires 'admin' access, which is granted using 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445799 @ retype -- Change rev type or archive (storage) type (unsupported) p4 retype [-l -n] -t filetype file[revRange] Retype changes the filetype of each revision of the named files to the new specified filetype. 'filetype' may be a full or partial filetype. See 'p4 help filetypes'. The -l flag causes retype to change the archive (storage) type of the revisions instead. This involves actually moving the revision contents in the server archive. If there are any lazy copies of the revisions, they are updated as well. Note that changing the archive type to purge old revisions using the +S modifier or xtempobj is not allowed, as this would result in purging server archive files. The effects of retype -l can be viewed with 'p4 fstat -Oc' (undocumented). Note that to change both the filetype and the storage type, 'p4 retype' must be run twice: once without and once with the -l flag. The -n flag previews the operation. 'p4 retype' ignores files from remote depots. 'p4 retype' does not purge older revisions when a filetype is retyped to a '+Sn' type. Subsequent edits cause revisions to be purged. 'p4 retype' requires 'admin' access, which is granted by 'p4 protect'. 'p4 retype' is unsupported, because it cannot safely run concurrently with other 'p4 retype', 'p4 snap', or 'p4 obliterate' commands. @ @pv@ 0 @db.message@ @en@ 268445769 @ revert -- Discard changes from an opened file p4 revert [-a -n -k -c changelist#] file ... Revert an open file to the revision that was synced from the depot, discarding any edits or integrations that have been made. You must explicitly specify the files to be reverted. Files are removed from the changelist in which they are open. Locked files are unlocked. The -a flag reverts only files that are open for edit or integrate and are unchanged or missing. Files with pending integration records are left open. The file arguments are optional when -a is specified. The -n flag displays a preview of the operation. The -k flag marks the file as reverted in server metadata without altering files in the client workspace. The -c flag reverts files that are open in the specified changelist. @ @pv@ 0 @db.message@ @en@ 268445770 @ review -- List and track changelists (for the review daemon) p4 review [-c changelist#] [-t counter] 'p4 review' lists changelists that have not been reviewed before, as tracked by the specified counter. If the counter is omitted, 'p4 review' lists all changelists. (If a changelist# and counter are specified, 'p4 review' sets the counter to that changelist# and produces no output. This functionality has been superceded by the 'p4 counter' command.) 'p4 review' is not meant as an end-user command. It exists to support an automated change review daemon. @ @pv@ 0 @db.message@ @en@ 268445771 @ reviews -- List the users who are subscribed to review files p4 reviews [-c changelist#] [file ...] 'p4 reviews' lists all users who have subscribed to review the specified files, the files in the specified changelist, or all files (the default). To subscribe to review files, issue the 'p4 user' command and edit the 'Reviews field'. @ @pv@ 0 @db.message@ @en@ 268445796 @ search -- Search index (unsupported) p4 search words Search is an interface to the search engine that searches jobs. This command lists any index keys that contain the specified words. See also 'p4 help index'. @ @pv@ 0 @db.message@ @en@ 268445798 @ snap -- Snap (undo) archive lazy copies (unsupported) p4 snap [-n] file[revRange] ... [archivePath] Snap scans the specified file revisions for any revision that has an archive file that is a lazy copy. For each of these files the contents is copied into the revision's archive namespace. This operation increases the amount of space required for the archive but ensures that (manually) deleting any other part of the archive does not affect the specified revisions. If archivePath argument is specified, only lazy copies with content in that path are copied. The -n flag previews the operation without copying files or changing metadata. 'p4 snap' requires 'admin' access, which is granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445772 @ set -- Set variables in the registry (Windows only) p4 set [-s -S service] [var=[value]] 'p4 set' sets Perforce Windows registry variables to the specified values. If you omit the value, the variable is unset. By default, 'p4 set' lists variable settings. The -s flag sets variables for the whole system rather than for the user. This option requires NT administrator privilege. The -S service flag sets variables for the specified service. This option requires NT administrator privilege. On Mac OS X, 'p4 set' sets a Perforce variable as a user preference, and 'p4 set -s' sets the variable as a system preference. These preferences are stored in the com.perforce.environment property list in your ~/Library/Preferences folder, or in the system /Library/Preferences folder if 'set -s' was used. The '-S' flag has no effect on Mac OS X. Registry variable entries can be overridden by environment variables and (in some cases) flags on the command line. See 'p4 help environment' for a list of environment/registry variables. @ @pv@ 0 @db.message@ @en@ 268445815 @ shelve -- Store files from a pending changelist into the depot p4 shelve [files] p4 shelve -i [-f | -r] p4 shelve -r -c changelist# p4 shelve -c changelist# [-f] [file ...] p4 shelve -d -c changelist# [-f] [file ...] 'p4 shelve' creates, modifies or deletes shelved files in a pending changelist. Shelved files remain in the depot until they are deleted (using 'p4 shelve -d') or replaced by subsequent shelve commands. After 'p4 shelve', the user can revert the files and restore them later using 'p4 unshelve'. Other users can 'p4 unshelve' the stored files into their own workspaces. Files that have been shelved can be accessed by the 'p4 diff', 'p4 diff2', 'p4 files' and 'p4 print' commands using the revision specification '@@=change', where 'change' is the pending changelist number. By default, 'p4 shelve' creates a changelist, adds files from the user's default changelist, then shelves those files in the depot. The user is presented with a text changelist form displayed using the editor configured using the $P4EDITOR environment variable. If a file pattern is specified, 'p4 shelve' shelves the files that match the pattern. The -i flag reads the pending changelist specification with shelved files from the standard input. The user's editor is not invoked. To modify an existing changelist with shelved files, specify the changelist number using the -c flag. The -c flag specifies the pending changelist that contains shelved files to be created, deleted, or modified. Only the user and client of the pending changelist can add or modify its shelved files. The -f (force) flag must be used with the -c or -i flag to overwrite any existing shelved files in a pending changelist. The -r flag (used with -c or -i) enables you to replace all shelved files in that changelist with the files opened in your own workspace at that changelist number. Only the user and client workspace of the pending changelist can replace its shelved files. The -d flag (used with -c) deletes the shelved files in the specified changelist so that they can no longer be unshelved. By default, only the user and client of the pending changelist can delete its shelved files. A user with 'admin' access can delete shelved files by including the -f flag to force the operation. @ @pv@ 0 @db.message@ @en@ 268445773 @ submit -- Submit open files to the depot p4 submit [-r -s -f option] p4 submit [-r -s -f option] file p4 submit [-r -f option] -d description p4 submit [-r -f option] -d description file p4 submit [-r -f option] -c changelist# p4 submit -i [-r -s -f option] 'p4 submit' commits a pending changelist and its files to the depot. By default, 'p4 submit' attempts to submit all files in the 'default' changelist. Submit displays a dialog where you enter a description of the change and, optionally, delete files from the list of files to be checked in. To add files to a changelist, issue the p4 edit, add or delete command, specifying the changelist number. If the file parameter is specified, only files in the 'default' changelist that match the pattern are submitted. The -c flag submits the specified pending changelist, which can be created manually using the 'p4 change' command or automatically as the result of a failed attempt to submit the default changelist. The -d flag passes a description into the specified changelist rather than displaying the changelist dialog for manual editing. This option is useful for scripting, but does not allow you to add jobs or modify the default changelist. The -f flag enables you to override submit options that are configured for the client that is submitting the changelist. This flag overrides the -r (reopen)flag, if it is specified. See 'p4 help client' for details about submit options. The -i flag reads a changelist specification from the standard input. The user's editor is not invoked. The -r flag reopens submitted files in the default changelist after submission. The -s flag extends the list of jobs to include the fix status for each job, which becomes the job's status when the changelist is committed. See 'p4 help change' for details. Before committing a changelist, submit locks all the files being submitted. If any file cannot be locked, or if the submit fails, the files are left open in a newly-created pending changelist. Submit is atomic: if the operation succeeds, all files are updated in the depot. If the submit fails, no depot files are updated. @ @pv@ 0 @db.message@ @en@ 268445795 @ spec -- Edit spec definitions (unsupported) p4 spec [-d -i -o] type Edit any type of specification: branch, change, client, depot, group, job, label, spec, stream, trigger, typemap, or user. Only the comments and the formatting hints can be changed. Any fields that you add during editing are discarded when the spec is saved. 'p4 jobspec' is equivalent to 'p4 spec job', and any custom spec (include the job spec) can be deleted with 'p4 spec -d type'. @ @pv@ 0 @db.message@ @en@ 268445774 @ sync -- Synchronize the client with its view of the depot flush -- synonym for 'sync -k' p4 sync [-f -n -k -q ] [-m max] [file[revRange] ...] p4 sync [-n -p -q] [-m max] [file[revRange] ...] Sync updates the client workspace to reflect its current view (if it has changed) and the current contents of the depot (if it has changed). The client view maps client and depot file names and locations. Sync adds files that are in the client view and have not been retrieved before. Sync deletes previously retrieved files that are no longer in the client view or have been deleted from the depot. Sync updates files that are still in the client view and have been updated in the depot. By default, sync affects all files in the client workspace. If file arguments are given, sync limits its operation to those files. The file arguments can contain wildcards. If the file argument includes a revision specifier, then the given revision is retrieved. Normally, the head revision is retrieved. See 'p4 help revisions' for help specifying revisions. If the file argument includes a revision range specification, only files selected by the revision range are updated, and the highest revision in the range is used. Normally, sync does not overwrite workspace files that the user has manually made writable. Setting the 'clobber' option in the client specification disables this safety check. The -f flag forces resynchronization even if the client already has the file, and overwriting any writable files. This flag doesn't affect open files. The -n flag previews the operation without updating the workspace. The -k flag updates server metadata without syncing files. It is intended to enable you to ensure that the server correctly reflects the state of files in the workspace while avoiding a large data transfer. Caution: an erroneous update can cause the server to incorrectly reflect the state of the workspace. The -p flag populates the client workspace, but does not update the server to reflect those updates. Any file that is already synced or opened will be bypassed with a warning message. This option is very useful for build clients or when publishing content without the need to track the state of the client workspace. The -q flag suppresses normal output messages. Messages regarding errors or exceptional conditions are not suppressed. The -m flag limits sync to the first 'max' number of files. This option is useful in conjunction with tagged output and the '-n' flag, to preview how many files will be synced without transferring all the file data. @ @pv@ 0 @db.message@ @en@ 268445787 @ tag -- Tag files with a label p4 tag [-d -n] -l label file[revRange] ... Tag associates the named label with the file revisions specified by the file argument. After file revisions are tagged with a label, revision specifications of the form '@@label' can be used to refer to them. If the file argument does not include a revision specification, the head revisions is tagged. See 'p4 help revisions' for revision specification options. If the file argument includes a revision range specification, only the files with revisions in that range are tagged. Files with more than one revision in the range are tagged at the highest revision. The -d deletes the association between the specified files and the label, regardless of revision. The -n flag previews the results of the operation. Tag can be used with an existing label (see 'p4 help labels') or with a new one. An existing label can be used only by its owner, and only if it is unlocked. (See 'p4 help label'). To list the file revisions tagged with a label, use 'p4 files @@label'. @ @pv@ 0 @db.message@ @en@ 268445788 @ tickets -- Display list of session tickets for this user p4 tickets 'p4 tickets' lists all the tickets that have been granted to the user by 'p4 login'. @ @pv@ 0 @db.message@ @en@ 268445775 @ trigger -- see 'p4 help triggers' @ @pv@ 0 @db.message@ @en@ 268445776 @ triggers -- Modify list of server triggers p4 triggers p4 triggers -o p4 triggers -i 'p4 triggers' edits the table of triggers, which are used for change submission validation, form validation, external authentication, external job fix integration, and external archive integration. Triggers are administrator-defined commands that the server runs to perform the following: Validate changelist submissions. The server runs changelist triggers before the file transfer, between file transfer and changelist commit, or after the commit Validate shelve operations. The server runs shelve triggers before files are shelved, after files are shelved, or when shelved files have been discarded (via shelve -d). Manipulate and validate forms. The server runs form-validating triggers between generating and outputting the form, between inputting and parsing the form, between parsing and saving the form, or when deleting the form. Authenticate or change a user password. The server runs authentication triggers to either validate a user password during login or when setting a new password. Intercept job fix additions or deletions. The server run fix triggers prior to adding or deleting a fix between a job and changelist. Access external archive files. For files with the +X filetype modifier, the server runs an archive trigger to read, write, or delete files in the archive. The trigger form has a single entry 'Triggers', followed by any number of trigger lines. Triggers are executed in the order listed and if a trigger fails, subsequent triggers are not run. A trigger succeeds if the executed command exits returning 0 and fails otherwise. Normally the failure of a trigger prevents the operation from completing, except for the commit triggers, which run after the operation is complete. Each trigger line contains a trigger name, a trigger type, a depot file path pattern or form type, and a command to run. Name: The name of the trigger. For change triggers, a run of the same trigger name on contiguous lines is treated as a single trigger so that multiple paths can be specified. Only the command of the first such trigger line is used. Type: When the trigger is to execute: archive: Execute an archive trigger for the server to access any file with the +X filetype modifier. auth-check: service-check: Execute an authentication check trigger to verify a user's password against an external password manager during login or when setting a new password. auth-set: Execute an authentication set trigger to send a new password to an external password manager. change-submit: Execute pre-submit trigger after changelist has been created and files locked but prior to file transfer. change-content: Execute mid-submit trigger after file transfer but prior to commit. Files can be accessed by the 'p4 diff2', 'p4 files', 'p4 fstat', and 'p4 print' commands using the revision specification '@@=change', where 'change' is the pending changelist number passed as %%changelist%%. change-commit: Execute post-submit trigger after changelist commit. fix-add: Execute fix trigger prior to adding a fix. The special variable %%jobs%% is available for expansion and must be the last argument to the trigger as it expands to one argument for each job listed on the 'p4 fix' command. fix-delete: Execute fix trigger prior to deleting a fix. The special variable %%jobs%% is available for expansion and must be the last argument to the trigger as it expands to one argument for each job listed on the 'p4 fix -d' command. form-out: Execute form trigger on generation of form. Trigger may modify form. form-in: Execute form trigger on input of form before its contents are parsed and validated. Trigger may modify form. form-save: Execute form trigger prior to save of form after its contents are parsed. form-commit: Execute form trigger after it has been committed, allowing access to automatically generated fields (jobname, dates etc). It cannot modify the form. This trigger for job forms is run by 'p4 job' and 'p4 fix' (after the status is updated), 'p4 change' (if the job is added or deleted) and 'p4 submit' (if the job is associated with the change). The 'form-commit' trigger has access to the new job name created with 'p4 job', while the 'form-in' and 'form-save' triggers are run before the job name is created. The special variable %%action%% is available on the job 'form-commit' trigger command line, and is expanded when the job is modified by a fix. form-delete: Execute form trigger prior to delete of form after its contents are parsed. shelve-submit: Execute pre-shelve trigger after changelist has been created but prior to file transfer. shelve-commit: Execute post-shelve trigger after files are shelved. shelve-delete: Execute shelve trigger prior to discarding shelved files. Path: For change and submit triggers, a file pattern to match files in the changelist. This file pattern can be an exclusion mapping (-pattern), to exclude files. For form triggers, the name of the form (branch, client, etc). For fix triggers 'fix' is required as the path value. For authentication triggers, 'auth' is required as the path value. For archive triggers, a file pattern to match the name of the file being accessed in the archive. Note that, due to lazy copying when branching files, the name of the file in the archive can not be the same as the name of the file in the depot. Command: The OS command to run for validation. If the command contains spaces, enclose it in double quotes. The following variables are expanded in the command string: %%client%% -- the client issuing the command %%clienthost%% -- the hostname of the client %%clientip%% -- the IP address of the client %%serverhost%% -- the hostname of the server %%serverip%% -- the IP address of the server %%serverport%% -- the IP address:port of the server %%serverroot%% -- the value of the server's $P4ROOT %%user%% -- the user issuing the command %%changelist%% -- the changelist being submitted %%changeroot%% -- the root path of files submitted %%oldchangelist%% -- the pre-commit changelist number (More information can be gathered about the changelist being submitted by running 'p4 describe %%changelist%%'.) %%formfile%% -- path to temp file containing form %%formname%% -- the form's name (branch name, etc) %%formtype%% -- the type of form (branch, etc) %%action%% -- added/deleted/submitted on job form-commit %%jobs%% -- list of job names for fix triggers %%op%% -- read/write/delete for archive access %%file%% -- name of archive file %%rev%% -- revision of archive file The command's standard input is empty for change, shelve, fix, and auth triggers; it is the form contents for form triggers; and it is the file content for the archive trigger. If the command fails, the command's standard output (not error output) is sent to the client as the text of a trigger failure error message. If the command succeeds, the command's standard output is sent as an unadorned message to the client for all triggers except archive triggers; for archive triggers, the command's standard output is the file content. The -o flag writes the trigger table to the standard output. The user's editor is not invoked. The -i flag reads the trigger table from the standard input. The user's editor is not invoked. 'p4 triggers' requires 'super' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445777 @ typemap -- Edit the filename-to-filetype mapping table p4 typemap p4 typemap -o p4 typemap -i 'p4 typemap' edits a name-to-type mapping table for 'p4 add', which uses the table to assign a file's filetype based on its name. The typemap form has a single field, 'TypeMap', followed by any number of typemap lines. Each typemap line contains a filetype and a depot file path pattern: Filetype: See 'p4 help filetypes' for a list of valid filetypes. Path: Names to be mapped to the filetype. The mapping is specified as a file pattern, and use be an exclusion (-pattern) to exclude files. To match all files anywhere in the depot hierarchy, the pattern must begin with //... To match files with a specified suffix, use '//.../*.suffix' or '//....suffix' (four dots). Later entries override earlier entries. If no matching entry is found in the table, 'p4 add' determines the filetype by examining the file's contents and execution permission bits. The -o flag writes the typemap table to standard output. The user's editor is not invoked. The -i flag reads the typemap table from standard input. The user's editor is not invoked. 'p4 typemap' requires 'admin' access, which is granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445778 @ unlock -- Release a locked file, leaving it open p4 unlock [-c changelist#] [-f] [file ...] 'p4 unlock' releases locks on the specified files, which must be open in the specified pending changelist. If you omit the changelist number, the default changelist is assumed. If you omit the file name, all locked files are unlocked. By default, files can be unlocked only by the changelist owner. The -f flag enables you to unlock files in changelists owned by other users. The -f flag requires 'admin' access, which is granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445816 @ unshelve -- Restore shelved files from a pending change into a workspace p4 unshelve -s changelist# [-f -n] [-c changelist#] [file ...] 'p4 unshelve' retrieves shelved files from the specified pending changelist, opens them in a pending changelist and copies them to the invoking user's workspace. Unshelving files from a pending changelist is restricted by the user's permissions on the files. A successful unshelve operation places the shelved files on the user's workspace with the same open action and pending integration history as if it had originated from that user and client. The -s flag specifies the number of the pending changelist that contains the shelved files. If a file pattern is specified, 'p4 unshelve' unshelves files that match the pattern. The -c flag specifies the changelist to which files are unshelved. By default, 'p4 unshelve' opens shelved files in the default changelist. The -f flag forces the clobbering of any writeable but unopened files that are being unshelved. The -n flag previews the operation without changing any files or metadata. @ @pv@ 0 @db.message@ @en@ 268445779 @ user -- Create or edit a user specification p4 user [-f] [name] p4 user -d [-f] name p4 user -o [name] p4 user -i [-f] Create a new user specification or edit an existing user specification. The specification form is put into a temporary file and the editor (configured by the environment variable $P4EDITOR) is invoked. Normally, a user specification is created automatically the first time that the user issues any command that updates the depot. The 'p4 user' command is typically used to edit the user's subscription list for change review. The user specification form contains the following fields: User: The user name (read-only). Email: The user's email address (Default: user@@client). Update: The date the specification was last modified (read-only). Access: The date that the user last issued a client command. FullName: The user's real name. JobView: Selects jobs that are displayed when the user creates a changelist. These jobs can be closed automatically when the user submits the changelist. For a description of jobview syntax, see 'p4 help jobview' Reviews: The subscription list for change review. There is no limit on the number of lines that this field can contain. You can include the following wildcards: ... matches any characters including / * matches any character except / Password: The user's password. See 'p4 help passwd'. Type: Must be 'service' or 'standard'. Default is 'standard'. Once set, the user type cannot be changed. The -d flag deletes the specified user (unless the user has files open). The -o flag writes the user specification to the standard output. The user's editor is not invoked. The -i flag reads a user specification from the standard input. The user's editor is not invoked. The -f flag forces the creation, update or deletion of the specified user, and enables you to change the Last Modified date. By default, users can only delete or modify their own user specifications. The -f flag requires 'super' access, which is granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445780 @ users -- List Perforce users p4 users [user ...] [-l -a] [-m max] Lists all Perforce users or users that match the 'user' argument. The report includes the last time that each user accessed the system. The -m max flag limits output to the first 'max' number of users. The -a flag includes service users in the output. The -l flag includes additional information in the output. The -l flag requires 'super' access, which is granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445781 @ verify -- Verify that the server archives are intact p4 verify [-m maxRevs] [-q] [-u | -v | -z] file[revRange] ... For each revision of the specified files, 'p4 verify' reports revision-specific information and an MD5 digest of the revision's contents. See 'p4 help revisions' for help specifying revisions. By default, 'p4 verify' computes and displays the digest of each revision. If a revision cannot be reproduced (for example, if the file is missing from the archive), the revision's output line ends with MISSING! If there is a saved digest, 'p4 verify' compares it with the computed one. If they differ, the output line ends with BAD! The -m max flag specifies the maximum number of revisions to process. This option can be used with the -u flag to compute and save digests in batches. The -u flag computes and save the digest only for revisions that have no saved digest. The -v flag computes and saves the digest for each revision, regardless of whether the revision already has a saved digest. This option can be used to update the saved digest if the archive was deliberately changed. The -z flag optimizes digest computations by skipping revisions that have already been computed in the current pass. This optionis useful when the specified files contain lazy copies. The resulting output might report a lazy copy revision if it is the first revision in the sort order to access a common archive file. This option cannot be used with the '-v' or '-u' options. The -q flag minimizes command output, displaying only errors from mismatched digests or unreproducible revisions. The following command verifies all revisions of all archive files: p4 verify -qz //... Saved digests are used by 'p4 diff' rather than recomputing them. 'p4 verify' requires 'admin' access, which is granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445782 @ where -- Show how file names are mapped by the client view p4 where [file ...] Where shows how the specified files are mapped by the client view. For each argument, three names are produced: the name in the depot, the name on the client in Perforce syntax, and the name on the client in local syntax. If the file parameter is omitted, the mapping for all files in the current directory and below) is returned. Note that 'p4 where' does not determine where any real files reside. It only displays the locations that are mapped by the client view. @ @pv@ 0 @db.message@ @en@ 268445801 @ Zeroconf service support The following flags and environment variables configure both server and proxy processes p4d -0 When the Perforce server is registered as a Zeroconf service, the service-type is 'p4', which is visible in DNS Service browse mode Discovery as '_p4._tcp'. If mDNS is not available on the host, service registration fails and logs an error in the server log, after which server continues the startup process. The -0 (digit zero) flag enables Zeroconf registry at server start time, overriding any value set for the $P4ZEROCONF environment variable. When using the environment variable, the presence of the variable in the environment enables the service registry. The following identity flags can be used to configure Zeroconf registry settings: p4d -In name Specifies a unique name for your server. This name is displayed in 'p4 -ztag info' output and by DNS Service Discovery, if you register the process as a Zeroconf service. This flag overrides any value set for the $P4NAME environment variable. If the name includes spaces, double-quote it. p4d -Id description Specifies a description of your server. This description is displayed in 'p4 -ztag info' output and by DNS Service Discovery, if you register the process as a Zeroconf service. This flag overrides any value set for the $P4DESCRIPTION environment variable. If the description includes spaces, double-quote it. @ @pv@ 0 @db.message@ @en@ 268445802 @ For information on server configuration variables, see 'p4 help configurables'. For information about unsupported server parameters, see the 'configurables' section of 'p4 help undoc'. Change these values only as directed by Technical Support. @ @pv@ 0 @db.message@ @en@ 268445805 @ dbschema -- Report meta database information p4 dbschema [tablename[:tableversion]]... 'p4 dbschema' reports database structure information about the Perforce metadata. Super permission is required to execute this command. The command reports schema information for the metadata tables. By default, all current tables are reported. You can optionally specify table names and versions. The results are returned as tagged output. Table names are the file names that start with 'db.' @ @pv@ 0 @db.message@ @en@ 268445808 @ export -- Extract journal or checkpoint records p4 export -c token [-J prefix] [-f] [-l lines] [-F filter] [-T tableexcludelist] p4 export -j token [-J prefix] [-f] [-l lines] [-F filter] [-T tableexcludelist] p4 export -j token [-J prefix] -r [-F filter] [-T tableexcludelist] 'p4 export' extracts journal or checkpoint records from the Perforce metadata. Super permission is required to execute this command. This command extracts records from database journals or checkpoints. By default, the records are returned in tagged output. Compressed journals or checkpoints are not supported. The -j token flag specifies a journal number and optional position (journal number/offset) from which to start exporting. The -c token flag specifies a checkpoint number and optional position (checkpoint number#offset) from which to start exporting. The -f flag formats non-textual datatypes appropriately. The -r flag changes the output to raw format (journals only). The -J prefix flag specifies a file name prefix to match the one used with p4d -jc . The -l flag limits the number of lines (records) exported. The -F filter flag limits output to records that match the filter pattern. The -T flag specifies a list of database tables that are excluded from the exported output. To specify multiple tables, double-quote the list and separate the table names with spaces. The table names must start with "db." Note: to delimit transactions and indicate the end of the journal, additional fields are added to the tagged output. Note: The final record is a position record that specifies the position where subsequent records are located. When processing a checkpoint, a position can be either a continuation of the checkpoint position (if the line count option was supplied) or a journal number. When processing a journal, if the last record processed is the last record the server has written, an 'atend' tag is inserted. This tag indicates to a polling process that it must wait for more data before issuing the next export command. Note that this final record is not filtered. Note: Journal 'ex' records can have a 'markers' 'complete' tag added. This tag indicates that, when that transaction ended, there were no known outstanding transactions. Note: Raw journal output places the raw journal text in a 'data' tag. Other tags can indicate positions of transactional complete locations in the journal. @ @pv@ 0 @db.message@ @en@ 268445817 @ replicate -- poll for journal changes and apply them to another server p4 replicate [-j token][-s statefile][-i interval][-k -x -R] [-J prefix][-T tables excluded][-o output][command] This client command polls for new journal entries from a server and outputs them or invokes another command that pipes the journal records to a subprocess. The -j token flag specifies a journal number and optional position (journal number/offset) from which to start replicating. The -J prefix flag specifies a file name prefix to match the one used with p4d -jc . The -s statefile flag specifies a file that tracks the most recent journal position. The -i interval flag specifies a polling interval. A zero interval causes the client to check once and exit (default value is 2 seconds). The -k flag configures the pipe to the sub-process command to remain open across polling intervals. By default, the pipe to the sub- process is restarted for every record batch. The -x flag configures 'p4 replicate' to terminate when a journal rotation is detected. The -R flag causes the command to attempt reconnection to the server in the event of a connection loss or serious error. An interval must be given with this option. The -T flag specifies a quoted, space separated list of table names which should not be transferred for replication. The -o output flag specifies an output file where journal records are written in addition to the sub-process command. See Perforce Knowledge Base article 1099 for detailed usage. Super permission is required to run this command. @ @pv@ 0 @db.message@ @en@ 268445809 @ dbstat -- Display size or simple statistics for a database table p4 dbstat [-h] { -a | dbtable ... } p4 dbstat -s The -h flag displays a histogram showing the distances between leaf pages, enabling you to anticipate disk seeks required for sequential database scans. Dbstat scans only the internal node pages of the file, not the leaf or overflow pages, and thus reads only 1-5%% of the file. Use this command with caution: it locks out write access to the database table during its scan. The -a flag outputs histogram statistics for all tables. The -s flag returns the size of the database table files. This command requires 'super' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445810 @ logstat -- Report the size of the journal, error log, and audit log files p4 logstat Logstat reports the file size of the journal, errorLog and auditLog files. This command requires 'super' access, which is granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445811 @ lockstat -- Report lock status of database tables p4 lockstat Lockstat reports database tables that are currently locked for a read or write operation. This command requires 'super' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445812 @ logtail -- Display the last block(s) of the errorLog p4 logtail [-b blocksize] [-s starting offset] [-m maxBlocks] Logtail outputs the last block(s) of the errorLog and the offset required to get the next block when it becomes available. The -s flag option enables you to specify the offset from the beginning of the file (in bytes). The -b flag specifies the block size in bytes (default 8192). The -m flag specifies a maximum number of blocks to output. By default, the command outputs all blocks from the offset until the end of the file. The data is returned in the tagged field 'data', in blocks of the size specified by the blocksize parameter. The 'offset' field contains the start of the next block, which can be used with -s to request the next batch of errorLog data. This command requires 'super' access, which is granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445813 @ dbpack -- reorder database index pages (unsupported) p4 dbpack [-c pages -l level] { -a | dbtable... } Dbpack reorders database index pages so that leaf pages are sequential. The -c flag causes the operation to stop after the specified number of leaf pages are reordered. The -l flag is a threshold that must be exceded before an index page is reordered. Values for threshold can be: 0: index page more than 90%% full and 80%% out of order (default) 1: index page more than 50%% full and 50%% out of order 2: index page more than 0%% out of order The -a flag reorders all tables. @ @pv@ 0 @db.message@ @en@ 268445814 @ ping -- test network performance p4 ping [-f][-p pausetime][-c count][-t seconds][-i iterations] [-s send size][-r receive size] Ping sends messages from the server to the client and back, timing the round trips. The round trip time is typically too fast to time a single packet, so a number of packets are sent. Ping reports the time in milliseconds. The -c flag specifies the number of messages in a test. The -t flag specifies how long to transmit (maximum 6000 seconds). The -i flag specifies the number of times to repeat the test. The -f flag causes the server to transmit continuously, without waiting for one message to be confirmed before sending the next. The -p flag specifies how long to pause between tests: specify 0 for no pause (maximum wait 120 seconds). The -s flag specifies the server-to-client message size, up to a maximum value of 10,000,000 bytes The -r flag specifies the client-to server message size, up to a maximum value of 100,000 bytes Be advised that 'p4 ping' can flood the network with traffic. The 'ping' command requires admin privileges. @ @pv@ 0 @db.message@ @en@ 268445820 @ configure -- manage server configuration variables p4 configure set [#]variable=value p4 configure unset [#]variable } p4 configure show [allservers | | ] 'p4 configure set' sets the value of the specified configuration variable. For a list of configuration variables, see 'p4 help configurables'. Server names are useful when multiple servers share the table. The server name can be specified using P4NAME or -In. If the server name is omitted, the special server name 'any' is used, and the value is used by any server that is using this server root. 'p4 configure unset' removes the specified configuration variable. 'p4 configure show' displays the current configuration of this server. 'p4 configure show allservers' displays the persistent configuration variables for all servers. 'p4 configure show ' displays the setting(s) of the specified variable. 'p4 configure show ' displays the persistent configuration variables that are set for the specified server server. This command requires 'super' access, which is granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445825 @ pull -- cause this replica server to retrieve data from its target p4 pull [-u | -l | -J prefix] [-i ] 'p4 pull' instructs this replica server to retrieve either journal records or file contents from its target server. The -i flag causes the command to automatically repeat its action every N seconds. If -i is not specified, the command runs once, then exits. The -u flag causes the command to retrieve file content. If -u is not specified, the command retrieves journal records and applies them to this server. The -l flag displays information about pending file content transfers. The -J prefix flag can be used when pulling journal records to specify a file name prefix to match the one used with p4d -jc prefix. This command requires 'super' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445826 @ Perforce server configurables The Perforce server behavior can be controlled by setting configuration variables using the 'p4 configure set' command. The configuration variables that can be set include the following, in addition to environment variables (see 'p4 help environment'): Name Default Use ---- ------- --- db.replication none Replica metadata replication mode dbjournal.bufsize 16K Journal/checkpoint read/write size dbopen.nofsync 0 Disable fsync of db files dm.annotate.maxsize 10M Maximum revision size for default annotate dm.domain.accessupdate 300 Time interval to update domain access time dm.domain.accessforce 3600 Time interval to force domain access time dm.grep.maxrevs 10K Maximum number of revs that can be searched dm.shelve.maxfiles 10M Max number of files that can be shelved dm.shelve.maxsize 0 Limit size of a file that can be shelved dm.user.accessupdate 300 Time interval to update user access time dm.user.accessforce 3600 Time interval to force user access time dm.user.noautocreate 0 Restrict autocreation of users filesys.binaryscan 8K 'add' looks this far for binary chars filesys.bufsize 4K Client file I/O buffer size filesys.extendlowmark 32K Minimum filesize before preallocation(NT) filetype.maxtextsize 10M Maximum file size for text type detection lbr.bufsize 4K Archive file I/O buffer size lbr.replication none Replica depot contents replication mode lbr.verify.in 1 Verify contents from the client to server lbr.verify.out 1 Verify contents from the server to client minClient none Lowest client version that may connect minClientMessage none Message to issue for client-too-old monitor 0 Server monitoring level net.backlog 10 Maximum pending connections queue length net.mimcheck 1 Man-in-the-middle network security level net.tcpsize 64K TCP sndbuf/rcvbuf sizes set at connect rcs.nofsync 0 Disable fsync of RCS files security 0 User/password security level serviceUser none Intermediate service identity spec.hashbuckets 0 Hash spec domains to sub directories startup.N none Background 'pull' command(s) for replica statefile none Replica server state tracking file name @ @pv@ 0 @db.message@ @en@ 1092683777 @Unsupported librarian file type %lbrType%!@ @pv@ 0 @db.message@ @en@ 839976962 @Old revision %lbrRev% of tempobj %lbrFile% purged; try using head revision.@ @pv@ 0 @db.message@ @en@ 857933827 @%trigger% %op%: %result%@ @pv@ 0 @db.message@ @en@ 1092683877 @RCS no revision after %name%!@ @pv@ 0 @db.message@ @en@ 1109461094 @RCS checkin %file%#%rev% failed!@ @pv@ 0 @db.message@ @en@ 1092683879 @RCS checkout %file% failed!@ @pv@ 0 @db.message@ @en@ 1092683880 @RCS can't commit changes to %file%!@ @pv@ 0 @db.message@ @en@ 1092683881 @RCS diff %file% failed!@ @pv@ 0 @db.message@ @en@ 1075906666 @RCS editLineNumber past currLineNumber!@ @pv@ 0 @db.message@ @en@ 1075906667 @RCS editLineCount bogus in RcsPieceDelete!@ @pv@ 0 @db.message@ @en@ 1092683884 @RCS editLine '%line%' bogus!@ @pv@ 0 @db.message@ @en@ 1075906669 @RCS checkin author/state empty!@ @pv@ 0 @db.message@ @en@ 1075906670 @RCS EOF in @@ block!@ @pv@ 0 @db.message@ @en@ 1075906671 @RCS expected desc!@ @pv@ 0 @db.message@ @en@ 1109461103 @RCS expected %token%, got %token2%!@ @pv@ 0 @db.message@ @en@ 1075906672 @RCS expected EOF!@ @pv@ 0 @db.message@ @en@ 1075906673 @RCS expected optional revision!@ @pv@ 0 @db.message@ @en@ 1075906674 @RCS expected ;!@ @pv@ 0 @db.message@ @en@ 1092683891 @RCS lock on %file% failed!@ @pv@ 0 @db.message@ @en@ 1092683892 @RCS loop in revision tree at %name%!@ @pv@ 0 @db.message@ @en@ 1092683893 @RCS delta mangled: %text%!@ @pv@ 0 @db.message@ @en@ 1092683894 @RCS can't make directory for %file%!@ @pv@ 0 @db.message@ @en@ 1092683895 @RCS no branch to revision %rev%!@ @pv@ 0 @db.message@ @en@ 1092683896 @RCS no such branch %branch%!@ @pv@ 0 @db.message@ @en@ 1092683897 @RCS no such revision %rev%!@ @pv@ 0 @db.message@ @en@ 1092683899 @RCS expected revision %rev% missing!@ @pv@ 0 @db.message@ @en@ 1092683900 @RCS non-existant revision %rev% to delete!@ @pv@ 0 @db.message@ @en@ 1092683901 @RCS parse error at line %line%!@ @pv@ 0 @db.message@ @en@ 1075906686 @RCS log without matching revision!@ @pv@ 0 @db.message@ @en@ 1075906687 @RCS token too big!@ @pv@ 0 @db.message@ @en@ 824641664 @Result RCS file '%file%' is too big; change type to compressed text.@ @pv@ 0 @db.message@ @en@ 452987009 @%file% %rev% %type% %state% %action% %digest% %size% %process% %timestamp% %retries% %lastError%@ @pv@ 0 @db.message@ @en@ 857800705 @%operation%: %arg%: %errmsg%@ @pv@ 0 @db.message@ @en@ 857800706 @%operation%: %arg%: unknown errno %errno%@ @pv@ 0 @db.message@ @en@ 1092681733 @%handle%: too many handles!@ @pv@ 0 @db.message@ @en@ 1092681734 @%handle%: deleted handled!@ @pv@ 0 @db.message@ @en@ 1092681735 @%handle%: no such handle!@ @pv@ 0 @db.message@ @en@ 824311816 @Resource fork for %file% from server is empty.@ @pv@ 0 @db.message@ @en@ 807799809 @Partner exited unexpectedly.@ @pv@ 0 @db.message@ @en@ 824577027 @Listen %address% failed.@ @pv@ 0 @db.message@ @en@ 807799813 @Required positional parameter missing.@ @pv@ 0 @db.message@ @en@ 807799814 @RpcTransport: partner is not a Perforce client/server.@ @pv@ 0 @db.message@ @en@ 824577031 @Operation '%operation%' failed.@ @pv@ 0 @db.message@ @en@ 807799816 @RpcTransport: partial message read@ @pv@ 0 @db.message@ @en@ 1076235273 @Can't connect an existing connection!@ @pv@ 0 @db.message@ @en@ 1076235274 @Can't make outbound connection via stdio!@ @pv@ 0 @db.message@ @en@ 807799819 @TCP connection accept failed.@ @pv@ 0 @db.message@ @en@ 824577036 @TCP connect to %host% failed.@ @pv@ 0 @db.message@ @en@ 824577037 @%host%: host unknown.@ @pv@ 0 @db.message@ @en@ 824577038 @TCP listen on %service% failed.@ @pv@ 0 @db.message@ @en@ 807799823 @TCP receive failed.@ @pv@ 0 @db.message@ @en@ 807799824 @TCP send failed.@ @pv@ 0 @db.message@ @en@ 824577041 @%service%: service unknown.@ @pv@ 0 @db.message@ @en@ 1076235282 @Rpc buffer too big to send!@ @pv@ 0 @db.message@ @en@ 1093012499 @Internal function '%function%' unregistered!@ @pv@ 0 @db.message@ @en@ 1076235284 @Connection attempt on unopened rpc!@ @pv@ 0 @db.message@ @en@ 807799829 @TCP receive interrupted by client.@ @pv@ 0 @db.message@ @en@ 824253441 @Librarian checkout %lbrFile% failed.@ @pv@ 0 @db.message@ @en@ 824253442 @Librarian diff %lbrFile% failed.@ @pv@ 0 @db.message@ @en@ 824253443 @Librarian digest %lbrFile% failed.@ @pv@ 0 @db.message@ @en@ 824253444 @Librarian filesize %lbrFile% failed.@ @pv@ 0 @db.message@ @en@ 824253445 @Librarian checkin %lbrFile% failed.@ @pv@ 0 @db.message@ @en@ 807476230 @Librarian merge failed.@ @pv@ 0 @db.message@ @en@ 824384902 @No archive trigger defined for %lbrFile%.@ @pv@ 0 @db.message@ @en@ 807607303 @Root directory (set with $P4ROOT or -r flag) invalid.@ @pv@ 0 @db.message@ @en@ 807607304 @Licensing error -- invalid server IP address.@ @pv@ 0 @db.message@ @en@ 824253449 @%depotFile% became unlocked!@ @pv@ 0 @db.message@ @en@ 857807882 @%depotFile% was just locked by %user% on %client%!@ @pv@ 0 @db.message@ @en@ 1092688907 @%depotFile% missing integration record!@ @pv@ 0 @db.message@ @en@ 1092688909 @%toFile% got unresolved!@ @pv@ 0 @db.message@ @en@ 1109466126 @%depotFile% - can't %action% file!@ @pv@ 0 @db.message@ @en@ 805379087 @Must specify dump file.@ @pv@ 0 @db.message@ @en@ 805379088 @Must specify checkpoint/journal files.@ @pv@ 0 @db.message@ @en@ 805379089 @Unknown journaling flag. Try 'c', 'd', 'j' or 'r'.@ @pv@ 0 @db.message@ @en@ 805379090 @Unknown -x operation. Try 'f', 'i', 'u', 'v', or 'x'.@ @pv@ 0 @db.message@ @en@ 824253459 @%file%: metadata dump failed@ @pv@ 0 @db.message@ @en@ 824384880 @%count% out of sequence journals were not replayed@ @pv@ 0 @db.message@ @en@ 807738388 @You need a 98.2 or newer client to access as a password-protected user.@ @pv@ 0 @db.message@ @en@ 807672853 @Perforce password (P4PASSWD) invalid or unset.@ @pv@ 0 @db.message@ @en@ 805379379 @Password must be set before access can be granted.@ @pv@ 0 @db.message@ @en@ 805379393 @The security level of this server requires the password to be reset.@ @pv@ 0 @db.message@ @en@ 805379394 @Password not allowed at this server security level, use 'p4 login'.@ @pv@ 0 @db.message@ @en@ 807672854 @Unicode server permits only unicode enabled clients.@ @pv@ 0 @db.message@ @en@ 807672855 @Unicode clients require a unicode enabled server.@ @pv@ 0 @db.message@ @en@ 824253464 @Operation: %command%@ @pv@ 0 @db.message@ @en@ 824253465 @Date %date%:@ @pv@ 0 @db.message@ @en@ 805379098 @Unknown command. Try 'p4 help' for info.@ @pv@ 0 @db.message@ @en@ 805379401 @Illegal command usage. Try 'p4 help' for info.@ @pv@ 0 @db.message@ @en@ 807803931 @Handshake failed.@ @pv@ 0 @db.message@ @en@ 824581148 @Connection from %peerAddress% broken.@ @pv@ 0 @db.message@ @en@ 807541789 @Client side operation(s) failed. Command aborted.@ @pv@ 0 @db.message@ @en@ 822156318 @Usage: %usage%@ @pv@ 0 @db.message@ @en@ 807738399 @Client doesn't have necessary support for diff -s.@ @pv@ 0 @db.message@ @en@ 807738401 @Must upgrade to 98.2 p4win to access jobs.@ @pv@ 0 @db.message@ @en@ 807738670 @Must upgrade past 97.3 p4win for this operation.@ @pv@ 0 @db.message@ @en@ 838933538 @'jobs -s %status%' no longer supported; use 'jobs -e status=%status%.@ @pv@ 0 @db.message@ @en@ 805379107 @Can't add (-a) and delete (-d) at the same time.@ @pv@ 0 @db.message@ @en@ 807738404 @Only 99.1 or later clients support 'p4 passwd'.@ @pv@ 0 @db.message@ @en@ 807738678 @Only 2003.2 or later clients support 'p4 passwd' at this server security level.@ @pv@ 0 @db.message@ @en@ 807738679 @This operation is not permitted at this server security level.@ @pv@ 0 @db.message@ @en@ 805575992 @Your session has expired, please login again.@ @pv@ 0 @db.message@ @en@ 805576135 @Your password has expired, please change your password.@ @pv@ 0 @db.message@ @en@ 268442937 @'login' not necessary, no password set for this user.@ @pv@ 0 @db.message@ @en@ 285220154 @%ticket%@ @pv@ 0 @db.message@ @en@ 285220165 @User %user% logged in.@ @pv@ 0 @db.message@ @en@ 335551814 @User %user% ticket expires in %hours% hours %minutes% minutes.@ @pv@ 0 @db.message@ @en@ 335551815 @User %user% was authenticated by password not ticket.@ @pv@ 0 @db.message@ @en@ 285220155 @User %user% logged out.@ @pv@ 0 @db.message@ @en@ 805575998 @Your session was logged out, please login again.@ @pv@ 0 @db.message@ @en@ 807738687 @Only 2003.2 or later clients support 'p4 login' at this server security level.@ @pv@ 0 @db.message@ @en@ 807738703 @Only 2004.2 or later clients support 'p4 login' for external authentication.@ @pv@ 0 @db.message@ @en@ 807738723 @Only 2007.2 or later clients support 'p4 login' for single sign-on.@ @pv@ 0 @db.message@ @en@ 822222180 @Single sign-on on client failed: %result%@ @pv@ 0 @db.message@ @en@ 805444965 @Single sign-on on client failed: 'P4LOGINSSO' not set.@ @pv@ 0 @db.message@ @en@ 805576038 @Login invalid.@ @pv@ 0 @db.message@ @en@ 805576014 @Command unavailable: external authentication '%triggerType%' trigger not found.@ @pv@ 0 @db.message@ @en@ 805576016 @Cannot change password for another user with external authentication.@ @pv@ 0 @db.message@ @en@ 822221861 @User %user% doesn't exist.@ @pv@ 0 @db.message@ @en@ 805575718 @Password invalid.@ @pv@ 0 @db.message@ @en@ 805575719 @Passwords don't match.@ @pv@ 0 @db.message@ @en@ 805575988 @Password should be at least 8 characters in length.@ @pv@ 0 @db.message@ @en@ 805575989 @Password should be mixed case or contain non alphabetic characters.@ @pv@ 0 @db.message@ @en@ 822353265 @Authentication from zeroconf resolved port '%port%' not allowed!@ @pv@ 0 @db.message@ @en@ 822353325 @Problem with TCP connections between client and server@ @pv@ 0 @db.message@ @en@ 807738408 @Your client doesn't support the -as flag.@ @pv@ 0 @db.message@ @en@ 807738409 @Your client doesn't support the -v flag.@ @pv@ 0 @db.message@ @en@ 822418474 @Submit failed -- fix problems above then use 'p4 submit -c %change%'.@ @pv@ 0 @db.message@ @en@ 822418842 @Change has shelved files - use 'p4 shelve -d -c %change%', then try again.@ @pv@ 0 @db.message@ @en@ 805641259 @File(s) couldn't be locked.@ @pv@ 0 @db.message@ @en@ 805641260 @Merges still pending -- use 'resolve' to merge files.@ @pv@ 0 @db.message@ @en@ 805641261 @Out of date files must be resolved or reverted.@ @pv@ 0 @db.message@ @en@ 805313910 @Invalid +S modifier or xtempobj type used for changing librarian filetype. See 'p4 help retype'.@ @pv@ 0 @db.message@ @en@ 806427694 @No files to submit.@ @pv@ 0 @db.message@ @en@ 839195695 @'%trigger%' validation failed: %result%@ @pv@ 0 @db.message@ @en@ 285547882 @%result%@ @pv@ 0 @db.message@ @en@ 822418480 @Submit validation failed -- fix problems then use 'p4 submit -c %change%'.@ @pv@ 0 @db.message@ @en@ 822418481 @Submit aborted -- fix problems then use 'p4 submit -c %change%'.@ @pv@ 0 @db.message@ @en@ 806427698 @No files to submit from the default changelist.@ @pv@ 0 @db.message@ @en@ 841096546 @Can't copy %depotFile%%depotRev% - revision has been purged!@ @pv@ 0 @db.message@ @en@ 807541811 @Some file(s) could not be transferred from client.@ @pv@ 0 @db.message@ @en@ 857873873 @%clientFile% corrupted during transfer %clientDigest% vs %serverDigest%@ @pv@ 0 @db.message@ @en@ 806427972 @Files newly opened or reverted during submission.@ @pv@ 0 @db.message@ @en@ 838868310 @%clientFile% tampered with after resolve - edit or revert.@ @pv@ 0 @db.message@ @en@ 805379124 @Wildcard ... not allowed by 'p4 dirs'. Use * instead.@ @pv@ 0 @db.message@ @en@ 536943669 @See 'p4 help rename' for instructions on renaming files.@ @pv@ 0 @db.message@ @en@ 536878134 @This was report mode. Use -y to remove files.@ @pv@ 0 @db.message@ @en@ 536878426 @This was report mode (-n), no files were snapped (copied).@ @pv@ 0 @db.message@ @en@ 570432815 @Warning: could not undo lazy copy link '%target%' -> '%source%@ @pv@ 0 @db.message@ @en@ 805379419 @Obliterate -z option deprecated - use 'p4 snap' instead@ @pv@ 0 @db.message@ @en@ 822156759 @'%path%' has revision range (not compatible with -b).@ @pv@ 0 @db.message@ @en@ 285219895 @%text%@ @pv@ 0 @db.message@ @en@ 807607352 @Unlicensed server cannot start while over user/client quota.@ @pv@ 0 @db.message@ @en@ 301997113 @%command% %text%@ @pv@ 0 @db.message@ @en@ 807607354 @Must shutdown unlicensed server to add license.@ @pv@ 0 @db.message@ @en@ 824384975 @Maximum licensed files (%files%) exceeded.@ @pv@ 0 @db.message@ @en@ 824384976 @Maximum users/clients AND maximum files (%files%) exceeded.@ @pv@ 0 @db.message@ @en@ 807607768 @Unlicensed server cannot perform remote authentication.@ @pv@ 0 @db.message@ @en@ 807607772 @Files limited license cannot perform remote authentication.@ @pv@ 0 @db.message@ @en@ 318774609 @Perforce Server starting %date% pid %pid% %ver%[ %mode% mode].@ @pv@ 0 @db.message@ @en@ 318774610 @Perforce Server shutdown %date% pid %pid%.@ @pv@ 0 @db.message@ @en@ 285220180 @Perforce db files in '%root%' will be created if missing...@ @pv@ 0 @db.message@ @en@ 285219940 @Counter %counterName% deleted.@ @pv@ 0 @db.message@ @en@ 285219941 @Counter %counterName% set.@ @pv@ 0 @db.message@ @en@ 285219942 @%counterValue%@ @pv@ 0 @db.message@ @en@ 822156711 @Can't increment counter '%counterName%' - value is not numeric.@ @pv@ 0 @db.message@ @en@ 268442727 @Jobs fixed ... @ @pv@ 0 @db.message@ @en@ 268442728 @Affected files ... @ @pv@ 0 @db.message@ @en@ 268443001 @ Moved files ... @ @pv@ 0 @db.message@ @en@ 268442729 @ Differences ...@ @pv@ 0 @db.message@ @en@ 268442730 @@ @pv@ 0 @db.message@ @en@ 268443033 @Shelved files ... @ @pv@ 0 @db.message@ @en@ 268442731 @(... files differ ...)@ @pv@ 0 @db.message@ @en@ 805379364 @File argument(s) require filepath(s), see 'p4 help diff2'.@ @pv@ 0 @db.message@ @en@ 822090161 @%context%: invalid context length argument@ @pv@ 0 @db.message@ @en@ 838867378 @%context%: larger than maximum of %maxcontext%@ @pv@ 0 @db.message@ @en@ 285219948 @%value% words added/deleted.@ @pv@ 0 @db.message@ @en@ 285219949 @User name: %user%@ @pv@ 0 @db.message@ @en@ 285219950 @User name: %user% (illegal)@ @pv@ 0 @db.message@ @en@ 285219951 @Client name: %client%@ @pv@ 0 @db.message@ @en@ 285219952 @Client name: %client% (illegal)@ @pv@ 0 @db.message@ @en@ 285220289 @Client stream: %stream%@ @pv@ 0 @db.message@ @en@ 285219953 @Client host: %host%@ @pv@ 0 @db.message@ @en@ 285219954 @Current directory: %dirName%@ @pv@ 0 @db.message@ @en@ 285219955 @Client address: %clientAddr%@ @pv@ 0 @db.message@ @en@ 285219956 @Server address: %serverAddr%@ @pv@ 0 @db.message@ @en@ 285219957 @Server root: %serverRoot%@ @pv@ 0 @db.message@ @en@ 301997174 @Server date: %serverDate% %serverTimeZone%@ @pv@ 0 @db.message@ @en@ 301997175 @Server version: %id% (%idDate%)@ @pv@ 0 @db.message@ @en@ 285219960 @Server license: %license%@ @pv@ 0 @db.message@ @en@ 285220222 @Server license-ip: %licenseIp%@ @pv@ 0 @db.message@ @en@ 285220207 @Server uptime: %uptime%@ @pv@ 0 @db.message@ @en@ 268442761 @Client unknown.@ @pv@ 0 @db.message@ @en@ 285219978 @Client root: %root%@ @pv@ 0 @db.message@ @en@ 301997195 @Proxy version: %id% (%idDate%)@ @pv@ 0 @db.message@ @en@ 285219980 @Authorization server: %authServer%@ @pv@ 0 @db.message@ @en@ 285220210 @Changelist server: %changeServer%@ @pv@ 0 @db.message@ @en@ 285220266 @Case Handling: %caseHandling%@ @pv@ 0 @db.message@ @en@ 285220271 @Minimum Client Level: %minClient%@ @pv@ 0 @db.message@ @en@ 285220233 @%fileCount% messages in %time%@ @pv@ 0 @db.message@ @en@ 285220234 @%fileCount% messages of %fileSize% characters in %time%@ @pv@ 0 @db.message@ @en@ 285220235 @%time% for %fileCount% messages@ @pv@ 0 @db.message@ @en@ 285220236 @%time% for %fileCount% messages of %fileSize% characters@ @pv@ 0 @db.message@ @en@ 822091149 @ping remote buffers requires 9.2@ @pv@ 0 @db.message@ @en@ 822091169 @Invalid ping parameter@ @pv@ 0 @db.message@ @en@ 268442745 @Password updated.@ @pv@ 0 @db.message@ @en@ 268442746 @Password deleted.@ @pv@ 0 @db.message@ @en@ 268442747 @Password not changed.@ @pv@ 0 @db.message@ @en@ 285220241 @Shelving files for change %change%.@ @pv@ 0 @db.message@ @en@ 806428050 @No files to shelve from the default changelist.@ @pv@ 0 @db.message@ @en@ 822353300 @Only user '%user%' can purge this shelvelist.@ @pv@ 0 @db.message@ @en@ 822418837 @Shelve aborted -- fix problems then use 'p4 shelve -c %change%'.@ @pv@ 0 @db.message@ @en@ 806428054 @No files to shelve.@ @pv@ 0 @db.message@ @en@ 806428059 @No shelved files in changelist to delete.@ @pv@ 0 @db.message@ @en@ 285220252 @%change% files shelved.@ @pv@ 0 @db.message@ @en@ 823205271 @%depotFile% - warning: shelved file was modified during transfer!@ @pv@ 0 @db.message@ @en@ 301997464 @Shelve %change% [partially deleted, still contains %count% file(s).|deleted.]@ @pv@ 0 @db.message@ @en@ 838933917 @%clientFile% size greater than shelve allows (max %maxFiles%).@ @pv@ 0 @db.message@ @en@ 805641634 @Shelve validation failed -- fix problems then try again.@ @pv@ 0 @db.message@ @en@ 285284782 @%depotFile% - warning: shelve of +l file@ @pv@ 0 @db.message@ @en@ 268442748 @Specification not corrected -- giving up.@ @pv@ 0 @db.message@ @en@ 822353219 @Error in %domain% specification.@ @pv@ 0 @db.message@ @en@ 268442957 @Warning: couldn't archive to spec depot (%lbrFile%)@ @pv@ 0 @db.message@ @en@ 268442974 @Error parsing form text; check form-out triggers?@ @pv@ 0 @db.message@ @en@ 285219965 @Locking %unlockedCount% files ...@ @pv@ 0 @db.message@ @en@ 285219966 @%change% submitted.@ @pv@ 0 @db.message@ @en@ 301997183 @%change% renamed %newChange% and submitted.@ @pv@ 0 @db.message@ @en@ 285219968 @Submitting change %change%.@ @pv@ 0 @db.message@ @en@ 318774401 @%toFile% - %how% %fromFile%@ @pv@ 0 @db.message@ @en@ 285219970 @%toFile% - resolve skipped.@ @pv@ 0 @db.message@ @en@ 822091204 @%clientFile% tampered with before resolve - edit or revert.@ @pv@ 0 @db.message@ @en@ 285219971 @%job% ...@ @pv@ 0 @db.message@ @en@ 285219972 @%word%@ @pv@ 0 @db.message@ @en@ 285219973 @%path%@ @pv@ 0 @db.message@ @en@ 301997190 @%status% %path%@ @pv@ 0 @db.message@ @en@ 301997191 @%lower%: %data%@ @pv@ 0 @db.message@ @en@ 318774408 @%lower%-%upper%: %data%@ @pv@ 0 @db.message@ @en@ 807607433 @Monitor not currently enabled.@ @pv@ 0 @db.message@ @en@ 822156426 @Invalid session identifier: %id%@ @pv@ 0 @db.message@ @en@ 318774709 @For server '%serverName%', configuration variable '%variableName%' set to '%variableValue%'@ @pv@ 0 @db.message@ @en@ 301997494 @For server '%serverName%', configuration variable '%variableName%' removed.@ @pv@ 0 @db.message@ @en@ 805379511 @Configuration variable '%name%' may not be changed.@ @pv@ 0 @db.message@ @en@ 805379512 @Configuration variable '%name%' may not be set to '%value%'.@ @pv@ 0 @db.message@ @en@ 318774738 @No configurables have been set.@ @pv@ 0 @db.message@ @en@ 318774739 @No configurables have been set for server '%serverName%'.@ @pv@ 0 @db.message@ @en@ 822156748 @Stream '%stream%' is invalid, use -f to force check.@ @pv@ 0 @db.message@ @en@ 805379272 @Usage: admin { checkpoint | journal | stop | updatespecdepot }@ @pv@ 0 @db.message@ @en@ 805379275 @Usage: admin checkpoint [ -z ] [ arg ] @ @pv@ 0 @db.message@ @en@ 805379276 @Usage: admin journal [ -z ] [ arg ] @ @pv@ 0 @db.message@ @en@ 805379424 @Usage: admin updatespecdepot [ -a | -s type ]@ @pv@ 0 @db.message@ @en@ 805379432 @Usage: admin import [ -l ] [ -b batchsize ]@ @pv@ 0 @db.message@ @en@ 805379361 @Usage: annotate [ -aciIq -d ] files...@ @pv@ 0 @db.message@ @en@ 805379525 @Usage: archive -D depot [-n -h -p -q ] files...@ @pv@ 0 @db.message@ @en@ 805379277 @Usage: branch [ -d -f -i -o ] branchname@ @pv@ 0 @db.message@ @en@ 805379278 @Usage: branch -o branchname@ @pv@ 0 @db.message@ @en@ 805379279 @Usage: branch -d [ -f ] branchname@ @pv@ 0 @db.message@ @en@ 805379280 @Usage: branch -i@ @pv@ 0 @db.message@ @en@ 805379281 @Usage: change [ -d -i -o -s -t ] [ -f | -u ] [ changelist# ]@ @pv@ 0 @db.message@ @en@ 805379282 @Usage: change -d [ -f ] changelist#@ @pv@ 0 @db.message@ @en@ 805379283 @Usage: change -o [ -s ] [ -f ] [ changelist# ]@ @pv@ 0 @db.message@ @en@ 805379284 @Usage: change -i [ -s ] [ -f | -u ]@ @pv@ 0 @db.message@ @en@ 805379528 @Usage: change -t restricted | public [ -f | -u ] changelist#@ @pv@ 0 @db.message@ @en@ 805379285 @Usage: changes [-i -t -l -L -f -c client -m count -s status -u user] [files...]@ @pv@ 0 @db.message@ @en@ 805379286 @Usage: client [ -d -f -i -o -t template ] [ clientname ]@ @pv@ 0 @db.message@ @en@ 805379287 @Usage: client -o [ -t template ] clientname@ @pv@ 0 @db.message@ @en@ 805379288 @Usage: client -d [ -f ] clientname@ @pv@ 0 @db.message@ @en@ 805379289 @Usage: client -i [ -f ]@ @pv@ 0 @db.message@ @en@ 805379508 @Usage: configure { show [ allservers | | ] | set [#]variable=value | unset [#]variable }@ @pv@ 0 @db.message@ @en@ 805379522 @Usage: copy [ -c changelist# -n -r -s from -v ] [ -b branch to... | from to ]@ @pv@ 0 @db.message@ @en@ 805379523 @Usage: copy [ -c changelist# -n -r -s from -v ] -b branch [ to... ]@ @pv@ 0 @db.message@ @en@ 805379290 @Usage: counter [ -d -f -i ] counter_name [ value ]@ @pv@ 0 @db.message@ @en@ 805379496 @Usage: counter [ -i ] counter_name@ @pv@ 0 @db.message@ @en@ 805379291 @Usage: counters@ @pv@ 0 @db.message@ @en@ 805379491 @Usage: cstat [files...]@ @pv@ 0 @db.message@ @en@ 805379431 @Usage: dbpack [ -c pages -l 0|1|2 ] { -a | dbtable ... }@ @pv@ 0 @db.message@ @en@ 805379416 @Usage: dbstat [ -h ] { -a | dbtable ... } dbstat -s@ @pv@ 0 @db.message@ @en@ 805379292 @Usage: depot [ -d -i -o ] depotname@ @pv@ 0 @db.message@ @en@ 805379293 @Usage: depot -o depotname@ @pv@ 0 @db.message@ @en@ 805379294 @Usage: depot -d depotname@ @pv@ 0 @db.message@ @en@ 805379295 @Usage: depot -i@ @pv@ 0 @db.message@ @en@ 805379296 @Usage: depots@ @pv@ 0 @db.message@ @en@ 805379297 @Usage: describe [-d -s -S -f [changelist#...]@ @pv@ 0 @db.message@ @en@ 805379298 @Usage: diff [ -d -f -m max -s -t ] [files...]@ @pv@ 0 @db.message@ @en@ 805379299 @Usage: diff2 [ -d -q -t -u ] [ -b branchName ] file file2@ @pv@ 0 @db.message@ @en@ 805379300 @Usage: diff2 [ -d -q -t -u ] -b branchName [ [ file ] file2 ]@ @pv@ 0 @db.message@ @en@ 805379301 @Usage: diff2 [ -d -q -t -u ] file file2@ @pv@ 0 @db.message@ @en@ 805379302 @Usage: dirs [-C -D -H] dirs...@ @pv@ 0 @db.message@ @en@ 805379303 @Usage: branches/clients/labels [ -t ] [ -u user ] [ -e query -m max ]@ @pv@ 0 @db.message@ @en@ 805379423 @Usage: duplicate [ -n -q ] from[revRange] to@ @pv@ 0 @db.message@ @en@ 805379450 @Usage: export [ -f -r -F -j -c -l -J ]@ @pv@ 0 @db.message@ @en@ 805379304 @Usage: filelog [ -c changelist# -h -i -l -L -t -m maxRevs -s ] files...@ @pv@ 0 @db.message@ @en@ 805379305 @Usage: files/print [-o localFile -q] [-m max] files...@ @pv@ 0 @db.message@ @en@ 805379306 @Usage: fix [ -d ] [ -s status ] -c changelist# jobName ...@ @pv@ 0 @db.message@ @en@ 805379307 @Usage: fixes [ -i -m max -c changelist# -j jobName ] [files...] @ @pv@ 0 @db.message@ @en@ 805379308 @Usage: fstat [ -F filter -T fields -m max -r ] [ -c | -e changelist# ] [ -Ox -Rx -Sx ] file[rev]...@ @pv@ 0 @db.message@ @en@ 805379499 @Usage: grep [ -a -i -n -A after -B before -C context -t -s ] [ -v | -l | -L ] [ -F | -G ] -e pattern files...@ @pv@ 0 @db.message@ @en@ 805379309 @Usage: group [ -d -i -o ] groupname@ @pv@ 0 @db.message@ @en@ 805379310 @Usage: group -o groupname@ @pv@ 0 @db.message@ @en@ 805379311 @Usage: group -d username@ @pv@ 0 @db.message@ @en@ 805379312 @Usage: group -i@ @pv@ 0 @db.message@ @en@ 805379313 @Usage: groups [ -m max ] [ [ [ -i ] user | group ] | [ -v [ group ] ] ]@ @pv@ 0 @db.message@ @en@ 805379314 @Usage: have [files...]@ @pv@ 0 @db.message@ @en@ 805379315 @Usage: help [command ...]@ @pv@ 0 @db.message@ @en@ 805379316 @Usage: index [ -a attrib ] [ -d ] name@ @pv@ 0 @db.message@ @en@ 805379317 @Usage: info [-s]@ @pv@ 0 @db.message@ @en@ 805379318 @Usage: integrate [ -c changelist# -d -D -f -h -i -o -n -r -s from -t -v ] [ -b branch to... | from to ]@ @pv@ 0 @db.message@ @en@ 805379319 @Usage: integrate [ -c changelist# -d -D -f -h -i -o -n -r -s from -t -v ] -b branch [ to... ] @ @pv@ 0 @db.message@ @en@ 805379320 @Usage: integrated [ -r ] [ -b branch ] [ files... ]@ @pv@ 0 @db.message@ @en@ 805379376 @Usage: interchanges -f -l -t -r [ -b branch to... | from to ]@ @pv@ 0 @db.message@ @en@ 805379377 @Usage: interchanges -f -l -t -r [ -b branch to... ]@ @pv@ 0 @db.message@ @en@ 805379531 @Usage: istat [ -a -f -r ] stream@ @pv@ 0 @db.message@ @en@ 805379321 @Usage: job [ -d -f -i -o ] [ jobName ]@ @pv@ 0 @db.message@ @en@ 805379322 @Usage: job -d jobName@ @pv@ 0 @db.message@ @en@ 805379323 @Usage: job -o [ jobName ]@ @pv@ 0 @db.message@ @en@ 805379324 @Usage: job -i [ -f ]@ @pv@ 0 @db.message@ @en@ 805379325 @Usage: jobs [-e query -i -l -m count -r] [files...]@ @pv@ 0 @db.message@ @en@ 805379326 @Usage: jobspec [ -i -o ]@ @pv@ 0 @db.message@ @en@ 805379327 @Usage: label [ -d -f -i -o -t template ] labelname@ @pv@ 0 @db.message@ @en@ 805379328 @Usage: label -o [ -t template ] labelname@ @pv@ 0 @db.message@ @en@ 805379329 @Usage: label -d [ -f ] labelname@ @pv@ 0 @db.message@ @en@ 805379330 @Usage: label -i [ -f ]@ @pv@ 0 @db.message@ @en@ 805379331 @Usage: labelsync [-a -d -n -q] -l label [files...]@ @pv@ 0 @db.message@ @en@ 805379415 @Usage: license [ -i | -o ]@ @pv@ 0 @db.message@ @en@ 805379332 @Usage: lock [-c changelist#] [files...]@ @pv@ 0 @db.message@ @en@ 805379388 @Usage: login [ -a -p ] [ -s ] [ username ]@ @pv@ 0 @db.message@ @en@ 805379389 @Usage: logout [ -a ]@ @pv@ 0 @db.message@ @en@ 805379333 @Usage: logger [ -c sequence# ] [ -t counter_name ]@ @pv@ 0 @db.message@ @en@ 805379453 @Usage: logtail [ -b blocksize ] [ -s starting offset ] [ -m maxBlocks ]@ @pv@ 0 @db.message@ @en@ 805379334 @Usage: p4d -h for usage.@ @pv@ 0 @db.message@ @en@ 805379369 @Usage: monitor { show | terminate | clear }@ @pv@ 0 @db.message@ @en@ 805379370 @Usage: monitor terminate [arg]@ @pv@ 0 @db.message@ @en@ 805379371 @Usage: monitor clear [arg]@ @pv@ 0 @db.message@ @en@ 805379372 @Usage: monitor show [ -a -l -e ]@ @pv@ 0 @db.message@ @en@ 805379335 @Usage: add/edit/delete [-c changelist#] [ -d -f -k -n -v ] [-t type] files...@ @pv@ 0 @db.message@ @en@ 805379470 @Usage: add/delete [-c changelist#] [ -d -f -n -v ] [-t type] files...@ @pv@ 0 @db.message@ @en@ 805379336 @Usage: opened [ -a -c changelist# -C client -u user -m max ] [ files... ]@ @pv@ 0 @db.message@ @en@ 805379337 @Usage: passwd [ -O oldPasswd -P newPasswd ] [ username ]@ @pv@ 0 @db.message@ @en@ 805379338 @Usage: protect [ -i | -o ]@ @pv@ 0 @db.message@ @en@ 805379411 @Usage: protects [ -a | -g group | -u user ] [ -h host -m ] [ file ... ]@ @pv@ 0 @db.message@ @en@ 805379513 @Usage: pull [ -u | -l | -J prefix ] [ -i ]@ @pv@ 0 @db.message@ @en@ 805379339 @Usage: obliterate [-y ] files...@ @pv@ 0 @db.message@ @en@ 805379340 @Usage: revert [ -a -n -k -c changelist# ] files...@ @pv@ 0 @db.message@ @en@ 805379341 @Usage: reopen [-c changelist#] [-t type] files...@ @pv@ 0 @db.message@ @en@ 805379342 @Usage: resolve [ -af -am -as -at -ay -d -f -n -o -t -v ] [ files... ]@ @pv@ 0 @db.message@ @en@ 805379343 @Usage: resolved [ -o ] [files...]@ @pv@ 0 @db.message@ @en@ 805379526 @Usage: restore -D depot [-n] files...@ @pv@ 0 @db.message@ @en@ 805379421 @Usage: retype [ -l -n ] -t type files...@ @pv@ 0 @db.message@ @en@ 805379344 @Usage: review [ -c start_changelist# ] [ -t counter_name ]@ @pv@ 0 @db.message@ @en@ 805379345 @Usage: reviews [ -c changelist# ] [ files... ]@ @pv@ 0 @db.message@ @en@ 805379346 @Usage: search words ...@ @pv@ 0 @db.message@ @en@ 805379413 @Usage: sizes [ -a -S ] [ -s | -z ] [ -b blocksize ] [ -m max ] files...@ @pv@ 0 @db.message@ @en@ 805379471 @Usage: shelve [ -i [ -f | -r ] | -r -c changelist | -c changelist [ -d ] [ -f ] [ file ... ] ] [ files ] @ @pv@ 0 @db.message@ @en@ 805379472 @Usage: shelve -c changelist# [ -d [ -f ] [ file ... ] | -r | [ -f ] [ file ... ] ]@ @pv@ 0 @db.message@ @en@ 805379486 @Usage: shelve -i [ -f | -r ]@ @pv@ 0 @db.message@ @en@ 805379487 @Usage: shelve -r -c changelist#@ @pv@ 0 @db.message@ @en@ 805379488 @Usage: shelve [ files ]@ @pv@ 0 @db.message@ @en@ 805379417 @Usage: snap [ -n ] source target@ @pv@ 0 @db.message@ @en@ 805379374 @Usage: spec [ -d | -i | -o ] type@ @pv@ 0 @db.message@ @en@ 805379455 @Usage: stream [ -d -i -o -P parent -v ] [ -f | -u ] [ streamname ]@ @pv@ 0 @db.message@ @en@ 805379456 @Usage: stream -d [ -f ] streamname@ @pv@ 0 @db.message@ @en@ 805379457 @Usage: stream -i [ -f | -u ]@ @pv@ 0 @db.message@ @en@ 805379458 @Usage: stream -o streamname@ @pv@ 0 @db.message@ @en@ 805379459 @Usage: streams [ -F filter -T fields -m max ] [ streamPath... ]@ @pv@ 0 @db.message@ @en@ 805379347 @Usage: submit [ -i -s -r -f option ] [ -c changelist# | -d description ] [file] @ @pv@ 0 @db.message@ @en@ 805379348 @Usage: submit [ -r -f option ] -c changelist#@ @pv@ 0 @db.message@ @en@ 805379518 @Usage: submit [ -r -f option ] -d description [ file ] @ @pv@ 0 @db.message@ @en@ 805379349 @Usage: sync [-f -k -n -p -q] [-m max] [files...]@ @pv@ 0 @db.message@ @en@ 805379420 @Usage: sync [ -n -p ] [-m max] [files...]@ @pv@ 0 @db.message@ @en@ 805379400 @Usage: tag [-d -n] -l label files...@ @pv@ 0 @db.message@ @en@ 805379402 @Usage: attribute [-e -f -p] -n name [-v value] files...@ @pv@ 0 @db.message@ @en@ 805379507 @Usage: attribute -i [-e -f -p] -n name [file]@ @pv@ 0 @db.message@ @en@ 805379350 @Usage: triggers [ -i | -o ]@ @pv@ 0 @db.message@ @en@ 805379351 @Usage: typemap [ -i | -o ]@ @pv@ 0 @db.message@ @en@ 805379352 @Usage: unlock [ -f ] [-c changelist#] [files...]@ @pv@ 0 @db.message@ @en@ 805379475 @Usage: unshelve -s shelvelist# [ -f -n ] [-c changelist#] [file ...]@ @pv@ 0 @db.message@ @en@ 805379353 @Usage: user [ -f -d -i -o ] [ username ]@ @pv@ 0 @db.message@ @en@ 805379354 @Usage: user -o username@ @pv@ 0 @db.message@ @en@ 805379355 @Usage: user -d [ -f ] username@ @pv@ 0 @db.message@ @en@ 805379356 @Usage: user -i [ -f ]@ @pv@ 0 @db.message@ @en@ 805379357 @Usage: users [ -l -a ] [ -m max ]@ @pv@ 0 @db.message@ @en@ 805379358 @Usage: verify [ -m maxRevs ] [ -q ] [ -u | -v | -z ] files...@ @pv@ 0 @db.message@ @en@ 805379359 @Usage: where [files...]@ @pv@ 0 @db.message@ @en@ 805379360 @Usage: p4p -h for usage.@ @pv@ 0 @db.message@ @en@ 805379447 @Usage: move [-c changelist#] [ -f ] [ -k ] [-t type] from to@ @pv@ 0 @db.message@ @en@ 805379463 @Usage: ping [ -f -p ] [ -i iterations ] [ -t seconds ] [ -c messages] [ -s server_message_size ] [-r client_message_size]@ @pv@ 0 @db.message@ @en@ 805379515 @Service user may not login to all hosts.@ @pv@ 0 @db.message@ @en@ 807476514 @Server is too old for use with Proxy@ @pv@ 0 @db.message@ @en@ 807476515 @Proxy servers may not be chained together@ @pv@ 0 @db.message@ @en@ 285220133 @File %path% delivered from proxy server@ @pv@ 0 @db.message@ @en@ 807476518 @Remote authorization server access failed.@ @pv@ 0 @db.message@ @en@ 807476644 @Replica does not support this command.@ @pv@ 0 @db.message@ @en@ 807476645 @Replica can not upgrade automatically.@ @pv@ 0 @db.message@ @en@ 807476646 @Unknown Replica Option.@ @pv@ 0 @db.message@ @en@ 807476692 @Unknown replication mode '%mode%'.@ @pv@ 0 @db.message@ @en@ 807476693 @Missing replication mode: please specify %missingMode%.@ @pv@ 0 @db.message@ @en@ 807476694 @Unknown replication target '%target%'.@ @pv@ 0 @db.message@ @en@ 807476698 @Transfer of librarian file '%file%' failed.@ @pv@ 0 @db.message@ @en@ 807607591 @Proxy Cache directory (set with $P4PCACHE or -r flag) invalid.@ @pv@ 0 @db.message@ @en@ 807607592 @Proxy Does not support cacheing remote server access.@ @pv@ 0 @db.message@ @en@ 555949357 @Proxy could not update its cache. File is %file%@ @pv@ 0 @db.message@ @en@ 805379378 @User 'remote' is not allowed direct access to commands.@ @pv@ 0 @db.message@ @en@ 822156716 @Client is too old to use this server. %message%@ @pv@ 0 @db.message@ @en@ 536943947 @Must upgrade to 2004.2 p4 to access tickets.@ @pv@ 0 @db.message@ @en@ 807607628 @Command terminated by 'p4 monitor terminate'.@ @pv@ 0 @db.message@ @en@ 807607649 @Can't create forms - no 'spec' depot found.@ @pv@ 0 @db.message@ @en@ 285220201 @Imported %count% journal record(s).@ @pv@ 0 @db.message@ @en@ 270736750 @No tables locked.@ @pv@ 0 @db.message@ @en@ 539172213 @No journal or log files found.@ @pv@ 0 @db.message@ @en@ 539172229 @Perforce server is not logging to an errorLog.@ @pv@ 0 @db.message@ @en@ 304291188 @%name% %size% bytes@ @pv@ 0 @db.message@ @en@ 807738744 @Only 2009.1 or later clients support 'p4 move'.@ @pv@ 0 @db.message@ @en@ 807738793 @Only 2010.1 or later clients support 'p4 move -f'.@ @pv@ 0 @db.message@ @en@ 824384891 @Journal %number% is not available@ @pv@ 0 @db.message@ @en@ 824384892 @Checkpoint %number% is not available@ @pv@ 0 @db.message@ @en@ 807607684 @A journal or checkpoint number is required (-j or -c)@ @pv@ 0 @db.message@ @en@ 807607728 @The current journal may not be exported because journaling is disabled.@ @pv@ 0 @db.message@ @en@ 807607738 @Pull only allowed on replica servers.@ @pv@ 0 @db.message@ @en@ 268443081 @%file% %rev% %type% %state% %process% %timestamp%@ @pv@ 0 @db.message@ @en@ 822222268 @Field %field% doesn't exist.@ @pv@ 0 @db.message@ @en@ 822222269 @The list of fields may not be empty.@ @pv@ 0 @db.message@ @en@ 822156735 @Client '%client%' requires an application that can fully support streams.@ @pv@ 0 @db.message@ @en@ 838933977 @Currently only user '%user%' can submit to stream '%stream%'.@ @pv@ 0 @db.message@ @en@ 822156749 @%name% is not a valid sort attribute name.@ @pv@ 0 @db.message@ @en@ 805379534 @Too many sort attributes (only 2 allowed).@ @pv@ 0 @db.message@ @en@ 824384960 @Startup command '%cmd%' is unknown or invalid.@ @pv@ 0 @db.message@ @en@ 824384970 @Startup command failed: %message%@ @pv@ 0 @db.message@ @en@ 824384987 @Custom spec of type '%specType%' is not allowed. Set spec.custom=1 to override.@ @pv@ 0 @db.message@ @en@ 805379273 @Usage: admin copyin prefix@ @pv@ 0 @db.message@ @en@ 805379274 @Usage: admin copyout prefix@ @pv@ 0 @db.message@ @en@ 805379443 @Usage: tunables [ -a ]@ @pv@ 0 @db.message@ @en@ 268446721 @# A Perforce Branch Specification. # # Branch: The branch name. # Update: The date this specification was last modified. # Access: The date of the last 'integrate' using this branch. # Owner: The user who created this branch. # Description: A short description of the branch (optional). # Options: Branch update options: [un]locked. # View: Lines to map source depot files to target depot files. # # Use 'p4 help branch' to see more about branch views. @ @pv@ 0 @db.message@ @en@ 268446722 @# A Perforce Client Specification. # # Client: The client name. # Update: The date this specification was last modified. # Access: The date this client was last used in any way. # Owner: The user who created this client. # Host: If set, restricts access to the named host. # Description: A short description of the client (optional). # Root: The base directory of the client workspace. # AltRoots: Up to two alternate client workspace roots. # Options: Client options: # [no]allwrite [no]clobber [no]compress # [un]locked [no]modtime [no]rmdir # SubmitOptions: # submitunchanged/submitunchanged+reopen # revertunchanged/revertunchanged+reopen # leaveunchanged/leaveunchanged+reopen # LineEnd: Text file line endings on client: local/unix/mac/win/share. # View: Lines to map depot files into the client workspace. # # Use 'p4 help client' to see more about client views and options. @ @pv@ 0 @db.message@ @en@ 268446734 @# A Perforce Stream Specification. # # Stream: # Update: # Access: # Owner: # Name: # Parent: # Type: # Description: # Options: Stream Options: # allsubmit/ownersubmit [un]locked # Paths: # Remapped: # Ignored: # # Use 'p4 help stream' to see more about the stream command. @ @pv@ 0 @db.message@ @en@ 268446723 @# A Perforce Label Specification. # # Label: The label name. # Update: The date this specification was last modified. # Access: The date of the last 'labelsync' on this label. # Owner: The user who created this label. # Description: A short description of the label (optional). # Options: Label update options: locked or unlocked. # Revision: Optional revision specification to make an automatic label. # View: Lines to select depot files for the label. # # Use 'p4 help label' to see more about label views. @ @pv@ 0 @db.message@ @en@ 268446733 @# A Perforce License Specification. # # License: The license key. # License-Expires: Date at which the license expires. # Support-Expires: Date at which support expires. # Customer: Customer to whom this license is granted. # Application: Application that can use this license. # IPAddress: IP/Port address for license. # Platform: Platform. # Clients: Number of supported clients. # Users: Number of supported users. # # Use 'p4 help license' to see more about license specification. @ @pv@ 0 @db.message@ @en@ 268446724 @# A Perforce Change Specification. # # Change: The change number. 'new' on a new changelist. # Date: The date this specification was last modified. # Client: The client on which the changelist was created. Read-only. # User: The user who created the changelist. # Status: Either 'pending' or 'submitted'. Read-only. # Type: Either 'public' or 'restricted'. Default is 'public'. # Description: Comments about the changelist. Required. # Jobs: What opened jobs are to be closed by this changelist. # You may delete jobs from this list. (New changelists only.) # Files: What opened files from the default changelist are to be added # to this changelist. You may delete files from this list. # (New changelists only.) @ @pv@ 0 @db.message@ @en@ 268446725 @# A Perforce Depot Specification. # # Depot: The name of the depot. # Owner: The user who created this depot. # Date: The date this specification was last modified. # Description: A short description of the depot (optional). # Type: Whether the depot is 'local', 'remote', 'spec', or 'archive'. # Address: Connection address (remote depots only). # Suffix: Suffix for all saved specs (spec depot only). # Map: Path translation information (must have ... in it). # # Use 'p4 help depot' to see more about depot forms. @ @pv@ 0 @db.message@ @en@ 268446726 @# A Perforce Group Specification. # # Group: The name of the group. # MaxResults: Limits the rows (unless 'unlimited' or 'unset') any one # operation can return to the client. # See 'p4 help maxresults'. # MaxScanRows: Limits the rows (unless 'unlimited' or 'unset') any one # operation can scan from any one database table. # See 'p4 help maxresults'. # MaxLockTime: Limits the time (in milliseconds, unless 'unlimited' or # 'unset') any one operation can lock any database table when # scanning data. See 'p4 help maxresults'. # Timeout: A time (in seconds, unless 'unlimited' or 'unset') # which determines how long a 'p4 login' # session ticket remains valid (default is 12 hours). # PasswordTimeout: # A time (in seconds, unless 'unlimited' or 'unset') # which determines how long a 'p4 password' # password remains valid (default is unset). # Subgroups: Other groups automatically included in this group. # Owners: Users allowed to change this group without requiring super # access permission. # Users: The users in the group. One per line. @ @pv@ 0 @db.message@ @en@ 268446727 @# Perforce Protections Specification. # # Each line contains a protection mode, a group/user indicator, the # group/user name, client host id and a depot file path pattern. # A user gets the highest privilege granted on any line. # # Mode: The permission level or right being granted or denied. Each # permission level includes all the permissions above it, # except for 'review'. Each permission right only includes # the specific right and not all the lesser rights. Modes # preceded by '=' are rights; all other modes are levels. # # list - users can see names but not contents of files; # users can see all non-file related metadata # (clients, users, changelists, jobs, etc.) # # read - users can sync, diff, and print files # # open - users can add, edit, delete, and integrate files # # write - users can submit open files # # admin - permits those administrative commands and command # options that don't affect the server's security # # super - allows access to the 'p4 protect' command # # review - allows access to the 'p4 review' command; implies # read access # # =read - if this right is denied, users cannot sync, diff, # or print files # # =branch - if this right is denied, users are not permitted # to use files as a source for 'p4 integrate' # # =open - if this right is denied, users cannot open files # (add, edit, delete, integrate) # # =write - if this right is denied, users cannot submit open # files # # Group/User indicator: either 'group' or 'user'. # # Name: A Perforce group or user name; may be wildcarded. # # Host: The IP address of a client host; may be wildcarded. # # Path: The part of the depot being granted access. @ @pv@ 0 @db.message@ @en@ 268446728 @# Perforce Submit and Form Validating Trigger Specifications. # # Triggers: a list of triggers; one per line. Each line has four # elements: # # Name: The name of the trigger. # # Type: 'archive' external archive access triggers # 'auth-check' check authentication trigger # 'auth-set' set authentication trigger # 'change-submit' pre-submit triggers # 'change-content' modify content submit triggers # 'change-commit' post-submit triggers # 'fix-add' pre-add fix triggers # 'fix-delete' pre-delete fix triggers # 'form-in' modify form in triggers # 'form-out' modify form out triggers # 'form-save' pre-save form triggers # 'form-commit' post-save form triggers # 'form-delete' pre-delete form triggers # 'service-check' check auth trigger (service users) # 'shelve-submit' pre-shelve triggers # 'shelve-commit' post-shelve triggers # 'shelve-delete' pre-delete shelve triggers # # Path: For change-* or shelve-*triggers, a pattern to # match files in the changelist. # # For form-* triggers, the type of form: e.g. 'branch' # 'client', etc. # # For fix-* triggers use 'fix'. # # For auth-* triggers use 'auth'. # # For archive triggers, a file pattern to match the # file name being accessed. # # Command: The OS command to run for validation. If the # command contains spaces, the whole command must # be quoted. See 'p4 help triggers' for a list of # variables that can be expanded in the command # string. # # For example, # # Triggers: # example change-submit //depot/... "cmd %%changelist%%" # # See 'p4 help triggers' for more information about triggers. @