@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@ 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 2009.2.TRASH_ONLY 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@ 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!@ @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@ 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@ 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@ 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%'.@ @mx@ 2596 1262975099 @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@ 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@ 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@ 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@ 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@ 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@ 352327941 @%depotFile%%workRev% - %action% from %fromFile%%fromRev%@ @pv@ 0 @db.message@ @en@ 385882536 @%depotFile%%workRev% - %action% from %fromFile%%fromRev% using base %baseFile%%baseRev%@ @pv@ 0 @db.message@ @en@ 352327942 @%depotFile%%workRev% - %action%/sync from %fromFile%%fromRev%@ @pv@ 0 @db.message@ @en@ 352327943 @%depotFile%%workRev% - sync/%action% from %fromFile%%fromRev%@ @pv@ 0 @db.message@ @en@ 352328107 @%depotFile%%workRev% - sync/%action% from %fromFile%%fromRev% using base %baseFile%%baseRev%@ @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@ 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@ 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@ 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 ]record(s).@ @pv@ 0 @db.message@ @en@ 352327990 @Would delete [%onHave% client ][%onLabel% label ][%onInteg% integration ][%onWorking% opened ][%onRev% revision ]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%@ @mx@ 2596 1262975099 @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@ 822155760 @'%tag%' unknown or wrong number of fields for path-type.@ @pv@ 0 @db.message@ @en@ 838867441 @User '%user%' is not an owner of Stream '%stream%'; use -f to force update.@ @pv@ 0 @db.message@ @en@ 335550962 @Stream: %stream% title: %title% type: %type% parent: %parent% owner: %owner%@ @pv@ 0 @db.message@ @en@ 822090227 @Stream '%stream%' must begin with '//'.@ @pv@ 0 @db.message@ @en@ 822090228 @Stream '%stream%' is retired 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@ 855710210 @%loc% wildcards (*, ...) not allowed in %path% path: '%id%'.@ @pv@ 0 @db.message@ @en@ 838932995 @Positional wildcards (%%%%x) not allowed in %path% path: '%id%'.@ @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@ 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@ 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] 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@ 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@ 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 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 causes all output (and batch input for form commands with -i) to be formatted 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 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 client program to prefix each line of output with a tag (error, warning, info, text, exit) so as to make it amenable to 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 named file. If the file is named '-', then standard input is read. The -V flag displays the version of the p4 client command and exits. The -z tag option causes output of reporting commands to be in the same format as that generated 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 branch Create or edit a branch specification branches Display list of branches 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 counter Display, set, or delete a counter counters Display list of known counters 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 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 group Change members of a user group groups List groups (of users) have List revisions last synced help Print this 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) 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 rename Explains how to rename files reopen Change the type or changelist number of an opened file resolve Merge open files with other revisions or files resolved Show files that have been merged but not submitted 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 @ @mx@ 2596 1262975099 @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. NB: read locks the database during the entire operation! Normally database locks are not held during network I/O to the client. (NOTE: this is the last release for this command). 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 given with the '-b' flag. Each batch will only lock the tables which will change. The -l flag instructs import to write lock all database tables and will process 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. Note that it is not recommended to use this command to import large journal files since the entire file has to fit in memory. (NOTE: this is the last release for this command). p4 attribute Set per-revision attributes on revisions. See 'p4 help attribute'. 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 to switch the font to red or blue for words 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 to 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 due to the 'p4 move' command, by default filelog will follow moved files. p4 files -m max The '-m' flag limits files to the first 'max' number of files. p4 fstat [ -Oacedhiz ] [ -A pattern ] The -Oa flag shows attributes set by 'p4 attribute'. The -Oae flag shows 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 not yet integrated. See 'p4 help interchanges'. p4 integrate -1 -3 -I -C changelist# The flag '-1' can be supplied to the 'p4 integrate' command to force consideration of direct integration history only. The -I flag used to turn on indirect integration, but that is now default and only implies -i now. The -C changelist# flag considers only integration history from changelists at or below the given number, allowing you to ignore credit from subsequent integrations. The -3 flag uses the experimental version of the integrate engine new to 2009.1. p4 jobspec presets Preset values for job non-optional fields 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 enforced to be in the range 100-199, but any value over 10000 can be used as well. p4 obliterate [ -abh ] Obliterate has been given 3 new flags to help improve performance. The flag '-b' restricts files in the argument range to those that are branched and are not only the first revision but also the head revision. This flag is useful in removing old branches but keeping files of interest (i.e. those that were modified). The flag '-a' 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 using this flag will mean that the file content will not be removed, if the file was a branch, then its most likely the archival search was not necessary. This option is safe to use with the '-b' option. The flag '-h' 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 will take a long time. However this flag should not be used when obliterating branches/namespaces for reuse, since the old content on any client will not match the newly added repository files. p4 merge3 3-way file merge. See 'p4 help merge3'. p4 ping Causes the server to send simple messages to the client, timing the network transmission time. p4 refresh files... Old name for 'p4 sync -f #have'. p4 reresolve Old name for 'p4 resolve -f'. p4 resolve -dg The flag '-dg' can be used to change the default merge algorithm to be more guarded about merging adjacent chunks. When this option is specified expect more conflicts to show up, especially where changes in both 'yours' and 'theirs' are identical but then diverge. p4 retype Change revision or server archive type. See 'p4 help retype'. p4 search Search index. See 'p4 help search'. p4 sizes -m max The '-m' flag limits sizes to the first 'max' number of files. p4 snap Snap archive lazy copies. See 'p4 help snap'. p4 spec Edit spec definitions. See 'p4 help spec'. p4 submit -t The '-t' flag to submit will tamper check branch/sync files and files resolved with 'at' i.e. copy from/lazy copied files. This check can significantly slow submit. Imported files are never tamper checked. p4 sync -m max The '-m' flag limits sync to the first 'max' number of files. This is useful when used in conjuction with tagged output and the '-n' flag to preview how many files will be synced without transfering all the file data. p4 trigger 'auth-check-sso' The trigger type 'auth-check-sso' can be used to facilitate a single sign-on user authentication. There are two programs/scripts that are required with this configuration: client: Use the environment variable 'P4LOGINSSO' to point to a script that can be executed to obtain that users credentials or other information that the server-side trigger can verify. The script should write the message to the standard output (max length 128K). e.g. P4LOGINSSO = /Users/joe/bin/runsso server: Execute an authentication (sso) trigger that will get this message from the standard input and return an exit status of 0 (for verified) or otherwise failed. e.g. sso auth-check-sso auth "/secure/verify %%user%%" The user still has to type 'p4 login' to establish the sign-on, but no password prompting is necessary. If the server verifies the user as valid, they will be issued a Perforce ticket just as if they had logged in with a password. Pre-2007.2 clients are unable to 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 either its 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 tunables [ -a ] Displays list of server tunable parameters that have been set. The -a flag displays all parameters. See P4DEBUG=tunables below. p4 where -Ttag The flag '-Ttag' causes the where command to output text in the same 'tagged' format as that 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 given, the revisions can be modified with relative operators. Relative operators on #head (other than = and <=) aren't yet allowed. Further, up to 4 revision specifications (separated by ,s) are allowed: the implied operator on the first is >=; thereafter <=. Note that you will need to 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 Anywhere a revision can be given, it can be given as #action to select all those revisions with that action. It isn't relative, however: #action cannot be used effectively in a revision range. Note that 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 can be useful for lots of very small files. There is currently no special support for backing up or recovering 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 suggest to p4win the form formatting. Each row of the Format field consists of a three words: field, order, and format. The order is an integer (starting at 1) indicating the display order; the display order is undefined without this. The format is: normal, L, R, or I; for full line, left half, right half, indented. If a right field follows a left, they go on the same line. JobStatus field on 'p4 change', 'p4 submit' 'p4 change' and 'p4 submit' forms have a 'JobStatus' field not normally displayed. This field sets the fix status for all jobs, rather than using the default 'closed'. The fix status can be set per-job with undoc 'p4 change -s' and 'p4 submit -s' (q.v.). p4 -zmaxLockTime=n command p4 -zmaxResults=n command p4 -zmaxScanRows=n command Overrides the user's maxLockTime/maxResults/maxScanRows for the command. p4 -R causes all output (and batch input for form commands with -i) to be formatted as marshalled Ruby hash objects. p4d -Cn Forces the server to operate in case-sensitive (n=0) on Windows or case-insensitive (n=1) mode on Unix. -Cn2 is an experimental 'hybrid' order: case folding but uniqueness preserving. Changing modes once a database is created will produce an error. p4d -jrc journal This variation of 'p4d -jr' changes the recover operation. The size of each batch of journal records is increased until a marker is seen indicating that all transactions are complete then only the database tables which will be changed are locked and the changes applied, then the tables are unlocked. This provides consistent database updating and allows system use while a journal is being applied. p4d -jds dumpfile Dumps the server metadata to the given file like p4d -jd but ignore the table indexes and read in file system order rather than data order. This may be useful for recovery should the btree index structure become corrupt. This is a recovery procedure not meant for normal production operation. Such dumps when restored do not compact the btrees as well as regular checkpoints and such restores take longer to complete. p4d -xf bugno Updates the server data to fix problems due to bugno. Current values of bugno are: 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 normally done automatically with p4d -xu. Try 'p4d -xU help' for a list of steps. This can be used to rebuild certain tables (like db.archmap). p4d -xx [ table1 [ table2 ] ] Performs a consistency check between table pairs, producing a file jnl.fix with '@@dv@@' and '@@pv@@' records which, when read in with p4d -jr, would eliminate the inconsistencies. If table names are given, only those are checked. The jnl.fix file should be checked for accuracy before attempting any updates. p4d -xv Does a low-level db verify. p4d -xr Does a low-level db verify and repair. Use only as a last resort if checkpoint and journal are not available. p4d -f -jr files... The -f flag to -jr causes it to ignore failures to delete records (due to corrupted tables or using the wrong journal). Normally, p4d -jr bails if it can't delete a record as indicated by the journal. 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. The default is 5000, and it can be set to 1 to force serial processing as with before release 2005.1. p4d -p -jd Adding a -p flag to the -jd server invocation will cause the server to attempt to output a metadata dump in a form compatible with an older server version. The earliest version which might work is 2005.1 which is server level 19. p4d -m rcsfiles... Dumps RCS metadata from files, in 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 which is then replaced with an identical revision numbered revision. Using this option will cause problems if head revisions are obliterated. However, the proxies cache can be pre-loaded by copying the server's archive files if this flag is given to start the proxy. p4p -w ... Start the Perforce Proxy with a read-only cache. This flag starts the proxy where it will never update its cache. This might be useful if the cache is updated through other ways such as a WAN NFS or other system level remote filesystem method. P4AUTH=central-server-address P4AUTH directs the server to refer to a central Perforce server for user authentication, so as to share user, group, protection, review, and licensing information. The outer server will use the central server's data for licensing (counting) and authenticating users; it will append the central server's protection table to its own (given the central server's protections precedence); it will consult the central server for user and review data for 'p4 review' and 'p4 reviews'; and it will forward wholesale the commands 'p4 group', 'p4 groups', 'p4 passwd', 'p4 user', 'p4 users', 'p4 login' and 'p4 logout' to the central server for processing. P4AUTH is set in the outer server's environment to the address of the central server. It may also be passed to the outer server with the -a flag. Both servers must be 2002.2 or greater. The outer server must be 2006.2 or greater for 'p4 review' and 'p4 reviews'. There are a number of limitations: setting P4AUTH immediately masks any local user/group information (unsetting it unmasks it); 'p4 review' and 'p4 reviews' require remote depot access enabled for the 'remote' user on the central server; and protections carried out in the central server based on the client IP address for forwarded commands must be granted using the IP address prefixed by the string 'proxy-' to distinguish them from trusted, non-forwarded clients. Protections for non-forwarded commands are enforced by the outer server and use the plain client IP address, even if they come from the central server. P4CHANGE=central-server-address P4CHANGE directs the server to refer to a central Perforce server for the global changelist counter. The outer server will use the central server's 'change' counter for the 'p4 change' command and for 'p4 submit'. The outer server's change counter will always be updated to the latest value that it has seen. P4CHANGE is set in the outer server's environment to the address of the central server. It may also be passed to the outer server with the -g flag. Both servers must be 2008.1 or greater. 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 to P4LOG server commands. server=2 logs command completion. Must be set in server's environment. P4DEBUG=tunables A number of server parameters can be tuned, by setting 'tunables' to a list of variable=value pairs separated by commas. These values should only be changed under the guidance of technical support. See 'p4 help tunables' for a list of these variables. @ @mx@ 2596 1262975099 @pv@ 0 @db.message@ @en@ 268445712 @ Environment variables used by Perforce: Variable Defines For more information see -------- ------- ------------------------ P4AUDIT name of server audit file p4d -h 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 p4 help usage P4CONFIG name of configuration file Command Reference Manual P4DESCRIPTION text description for server p4 help zeroconf 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 client p4 help usage P4JOURNAL name of server journal file p4d -h P4LANGUAGE language for text messages p4 help usage P4LOG name of server log file p4d -h P4MERGE merge program to use on client p4 help resolve P4MERGEUNICODE merge program to use on client p4 help resolve P4NAME provide a unique server name p4 help zeroconf P4PAGER pager for 'p4 resolve' output p4 help resolve P4PASSWD user password passed to server p4 help passwd P4PORT port client connects to p4 help info or server listens on p4d -h P4ROOT server root directory p4d -h P4TARGET target server for proxy Command Reference Manual P4TICKETS location of tickets file Command Reference Manual P4USER user name p4 help usage P4ZEROCONF register with zeroconf p4 help zeroconf PWD current working directory p4 help usage TMP, TEMP directory for temporary files Command Reference Manual See 'p4 help set' for details specific to Windows. The syntax for setting an environment variable depends on the OS/shell. Note that many shells allow the setting of shell variables separate from environment variables - Perforce cannot see the shell variable, only the environment variable. If you are a typical user then the only variables of interest are $P4CLIENT, $P4PORT and $P4PASSWD. @ @pv@ 0 @db.message@ @en@ 268445713 @ File types supported by Perforce: Perforce understands a variety of files, indicated by a file's filetype, which determines how the file is handled on both the client and the server. A filetype can be given either alone as 'type' or with specific modifiers 'type+mods'. A partial filetype, used to modify other filetypes, is just the modifiers '+mods'. The following are the base 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 type aliases exist 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' can take a '-t filetype' to specify the filetype. Without -t 'p4 add' also looks for a filetype using the name-to-type mapping table managed by 'p4 typemap'. For a default 'p4 edit' and 'p4 reopen' reuse the current file filetype, and 'p4 add' senses the filetype by examining the file's contents and execute permission bits. If a filetype is given as a partial filetype, with '+mods' only, then that filetype is combined with, rather than replaces, the default. Most modifiers are simply added to the default type, but the storage modifiers +C, +D, and +F replace the storage method. It is not possible to remove a modifier with a partial filetype, for example to remove +x if the file was sensed to be executable. For that, the whole filetype must be given. @ @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 which jobs to display. Also, the 'p4 user' form contains a JobView field which selects which jobs are to be presented during changelist creation for automatic closing upon changelist submission. 'p4 job' indexes all whitespace-separated words, and then any 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 allows searching for a range of dates. In its simplest form, a job view can contain a list of words, separated by spaces, that must appear in a job for it to be selected. For a match to occur all words must appear somewhere in the job, not including date fields: JobView: GUI redrawing bug p4 jobs -e 'GUI redrawing bug' To select a particular field, the 'field=word' syntax may be used: JobView: GUI redrawing status=open Logical operators & (and), | (or), ^ (not), and () (grouping) may also be used; spaces remain a low-precedence 'and' operator: JobView: redrawing (type=bug|type=sir) status=open The ^ (not) operator cannot be used alone or with | (or), only in conjuction with & (and) or space (and): JobView: type=bug & ^status=closed Comparative operators >, >=, <, <=, and = are permitted. Because they succeed if any word in the field matches, only the = operator is useful against fields containing blocks of text: JobView: priority<=b description=gui Text searches may embed the wildcard *, which matches anything: JobView: redraw* type=bug To match operator characters, you can escape them with \. Date fields may be searched using comparative operators. Dates are of the form yyyy/mm/dd or yyyy/mm/dd:hh:mm:ss. If a specific time is not given, 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: Some file-related Perforce client commands can limit their actions to specific file revisions. A revision specification is tacked onto the end of the filename, and is one of the following: #rev - A revision number. @@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, so if you want to include all events on that day refer to the next day. #rev has special variants, to be used literally: #none - A nonexistent revision (also #0). #head - The current head revision. #have - The revision on the current client. In all cases, if a file doesn't exist at the given revision number it appears as if the file doesn't exist at all. Thus using a label to refer to a file that isn't in the label is indistinguishable from referring to file that doesn't exist at all. If no revision specification is given, the default is usually #head. A revision specification can be given without a filename. This limits the command's action to the specified revision of all files in the depot or in the client's workspace. Thus #head refers to the head revision of all files in the depot, and @@label refers to the revisions of all files in the named label. Some commands can limit their actions to a range of revision numbers, rather than just a single revision. A revision range is two revision specifications, separated by a comma (,). If a single revision is given where a revision range is expected, then the named revision specifies the end of the range and the beginning is left at #1. 'p4 obliterate' is an exception: a single revision means exactly that revision. If no revision number or range is given where a revision range is expected, the default is all revisions. @ @pv@ 0 @db.message@ @en@ 268445716 @ Perforce views: A Perforce view maps file names from the depot into the client workspace (for a client view) or into another part of the depot (for a 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, meaning it begins with // and the client or depot name, and is followed by the actual file name within the client or depot. Perforce syntax uses /'s as directory separators. e.g. //depot/dir/file.c Mappings can contain wildcards, as long as the wildcards are matched between the left and right sides. The 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, then the later mapping line overrides the earlier one, excluding any files from the earlier mapping. A mapping line that begins with a + overlays the later mapping on the earlier one: if files match both the earlier and later mappings, then the file matching the later mapping is used. Overlay mappings are only allowed on client views, and make it possible to map multiple server directories to the same client directory. A mapping line that begins with a - specifically excludes those files that match that mapping. @ @pv@ 0 @db.message@ @en@ 268445717 @ Dealing with super-user imposed limits on data access: The Perforce super-user can limit the amount of data the server will handle on behalf of client operations, so as to avoid swamping servers with inadvertent requests against large datasets. There are three limits: MaxResults, MaxScanRows, and MaxLockTime. MaxResults limits the rows of resulting data buffered and prevents the server from using excessive memory. MaxScanRows limits the 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 waiting for any subsequent table locks. All three limits are set for groups of users by the 'p4 group' command. If an operation exceeds any of these limits, the whole operation fails. For naive users, MaxResults should be larger than the number of files anticipated in any one of their individual client workspaces, and MaxScanRows should be 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 while not interfering with normal use. MaxLockTime should probably be in the 1000-30000 (1-30 second) range. The following table describes what commands are subjected to these limits, what entity is counted, and 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 be several times over the number of actual files. Restrict the operation by using more restrictive wildcards on the command line, so as to include fewer files, or by using a revision range (if permitted). (3) If the data to describe a change exceeds the limit, 'describe' simply cannot be run. (4) 'labelsync' limits files. Use more restrictive wildcards and 'p4 labelsync -a' to build up the label in pieces. @ @pv@ 0 @db.message@ @en@ 268445719 @ The Perforce clients and server have an optional mode of operation where 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 controls the client character set. Supported values 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) 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 Unicode mode. In Unicode mode, all non-file data (identifiers, descriptions, etc) and the content of files of type 'unicode' are translated between the P4CHARSET character set on the client 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, use of the command line 'p4' will require setting P4COMMANDCHARSET to a non-utf-16 value. This allows P4CHARSET to control the translation of file revision contents while using a command line system which is not utf-16 based as most commands lines are not utf-16 compatible. All UTF-16 values will honor a file's Byte-Order-Mark when a file is being read, but when a file is being written the specified UTF-16 format will be followed. @ @mx@ 2596 1262975099 @pv@ 0 @db.message@ @en@ 268445814 @ 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, Geri Clucas, Peter Kreps, Mark Mears, Michael Alyn Miller, Mike Schonberg, Andy Shebanow, David Sielaff, 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# ] [ -f -n ] [ -t filetype ] file ... Open a new 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. The file must either not exist in the depot, or it must be deleted at the current head revision. Files may be deleted and re-added. If the -c flag is given the open files are associated with the specified pending changelist number; otherwise the open files are associated with the default changelist. If file is already open it is moved into the specified pending changelist. It is not permissible to reopen a file for add unless it was already open for add. If -t filetype is given, the file is added as that filetype. Without -t 'p4 add' looks for a filetype using the name-to-type mapping table managed by 'p4 typemap'. For a default 'p4 add' senses the filetype by examining the file's contents and execute permission bit. If the filetype given by -t or in the typemap table is a partial filetype, that partial filetype will modify the filetype sensed by 'p4 add'. See 'p4 help filetypes'. If the -f flag is given then filenames that contain wildcards are permitted. Filenames added to the repository that contain these special wildcard characters '@@', '#', '%' or '*' will have those characters formatted into ascii hexadecimal representation. The only way of referring to those files once added will be to use the formatted version, the local filesystem name will not be recognized. The -n flag displays what would be opened for add without actually 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. It is equivalent to 'p4d -jc'. 'p4 admin journal' causes the server to save the journal to a numbered journal file and then truncate it. It is equivalent to 'p4d -jj'. The -z flag causes the checkpoint and saved journal to be saved in compressed (gzip) format, with the '.gz' suffix on the file names. If a prefix is specified, the files will be named prefix.ckp.n and prefix.jnl.n respectively, where n is a sequence number. Without prefix, the default filenames checkpoint.n and journal.n will be used. 'p4 admin stop' stops the server, terminating any requests currently running. It first locks the database to ensure that no updates are taking place, but otherwise is brutal as it does not wait for users to finish what they are doing. (For NT users, this will work whether you are running Perforce as a server or a service.) 'p4 admin updatespecdepot' causes the server to archive forms (client, depot, branch, label, typemap, group, user, job) into the spec depot. If the '-a' flag is used then all of the form specification types are archived. If the '-s' flag option is used, then only the form type requested is archived. Note only forms that have not yet been archived will be 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 (given 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 Allows 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 branches are created with a default view that maps all depot files back into themselves. This view must be changed before the branch view is usable. A branch definition is used only by the 'p4 integrate' command. The -d flag deletes the named branch. The -o flag causes the named branch specification to be written to the standard output. The user's editor is not invoked. The -i flag causes a branch specification to be read from the standard input. The user's editor is not invoked. The -f flag can force the deletion of any branch; normally branches can only be deleted by their owner. -f also allows the last modified date to be set. The -f flag requires 'admin' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445783 @ annotate -- Print file lines along with their revisions p4 annotate [ -aciq -d ] file[revRange] ... Prints all lines of the named files, indicating what revision introduced each line into the file. If the file argument has a revision, then only revisions up to that revision are displayed. If the file argument has a revision range, then only revisions within that range are displayed. See 'p4 help revisions' for help specifying revisions. The -a flag includes both deleted files and lines no longer present at the head revision; in this case, both the starting and ending revision for each line is indicated. The -c flag tells annotate to output change numbers rather than revision numbers with each line. The -d changes 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 (i.e. a file branched on top of a deleted file), -i ignores those prior revisions and instead follows the source. -i implies -c. The -q flag suppresses the one-line header for each file. @ @pv@ 0 @db.message@ @en@ 268445791 @ attribute -- Set per-revision attributes on revisions (unsupported) p4 attribute [ -e -f -p ] -n name [ -v value ] files... Sets a user-managed attribute 'name' to 'value' on opened files. If -v isn't given the attribute is cleared (if set). Attributes can only be viewed with 'p4 fstat'. The -e flag indicates the 'value' is in hex. The -f flag sets the attribute on submitted files. The -p flag creates an attribute whose value will be propagated when the file is opened with 'p4 add', 'p4 edit', or 'p4 delete'. @ @pv@ 0 @db.message@ @en@ 268445724 @ branches -- Display list of defined branches p4 branches [ -u user ] [ -e nameFilter -m max ] Reports the list of all branches currently known to the system. Branches takes no arguments. The -u user flag limits branches to those owned by the named user. The -e nameFilter flag limits output to branches whose name matches the nameFilter pattern, e.g. -e 'svr-dev-rel*' The -m max flag limits output to the first 'max' number of branches. @ @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 as well as zeroconf (avahi/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 ] [ changelist# ] p4 change -i [ -s ] [ -f | -u ] 'p4 change' creates and edits changelists and their descriptions. With no argument, 'p4 change' creates a new changelist. If a changelist number is given, '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 discards a pending changelist, but only 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 only be deleted by the user and client who created it, or by using the -f flag. The -o flag causes the changelist specification to be written to the standard output. The user's editor is not invoked. The -i flag causes a changelist specification to be read from the standard input. The user's editor is not invoked. The -f flag can force the update or deletion of other users' pending changelists. -f can also force the deletion of submitted changelists once they have been emptied of files via 'p4 obliterate'. Normally, submitted changelists are immutable. 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 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 is not meant for end-users. It exists to support propagating information from an external defect tracking system. @ @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 -c client -m max -s status -u user Reports the list of all pending and submitted changelists currently known to the system. If files are specified, 'p4 changes' limits its report to changelists that affect those files. If the file specification includes a revision range, 'p4 changes' limits its report to submitted changelists that affect those particular revisions. See 'p4 help revisions' for help specify revisions. 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 produces long output with the full text of the changelist descriptions. The -L flag produces long output with the full text of the changelist descriptions truncated to 250 characters. The -c client flag limits changes to those on the named 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 limits changes to those owned by the named 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 ] With no argument 'p4 client' creates a new client view specification or edits an existing client specification. The client name is taken from the environment variable $P4CLIENT if set, or else from the current host name. The specification form is put into a temporary file and the editor (given by the environment variable $P4EDITOR) is invoked. If a name is given, the specification of the named client is used. 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 this specification was last modified. Access: The date 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 (given in local file system syntax), under which all client files will be placed. If you change this, you must physically relocate any files as well. The name "null" may be used to allow files to be mapped to multiple drives on Windows clients. 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 matches the main root is used anyway. 'p4 info' reports the applicable root. Options: Flags to change the client behavior. The defaults are marked with *. allwrite Leaves all files writable on the client; noallwrite * else only checked out files are writable. If set, files may be clobbered ignoring the clobber option below. clobber Allows '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 file nomodtime * modification time from 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 submitunchanged+reopen (default). revertunchanged Files that have content or type revertunchanged+reopen changes are submitted. Unchanged files are reverted. leaveunchanged Files that have content or type leaveunchanged+reopen changes are submitted. Unchanged files are moved to the default changelist. +reopen appended to the submit option flag will cause submitted files to be reopened on the default changelist. LineEnd: Set line ending character(s) for client text files. local Use mode 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: A mapping from the files in the depot to files in the client workspace. This is the mechanism by which you select what files you want on your client and where you want them to be. 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 yourself. Similarly, changing the 'LineEnd' option does not actually update the client files; you can refresh them with 'p4 sync -f'. The -d flag causes the named client to be deleted, as long as it has no opened files. The -f forces the delete. The -o flag causes the named client specification to be written to the standard output. The user's editor is not invoked. The -i flag causes a client specification to be read from the standard input. The user's editor is not invoked. The -t flag constructs the client's view by copying the named template client's view, instead of using the existing view or creating a new default view. It also copies the client options from the template client. The -f flag can force the updating of locked clients; normally locked clients can only be modified by their owner. -f also allows the last modified date to be set. The -f flag requires 'admin' access granted by 'p4 protect'. @ @mx@ 2596 1262975099 @pv@ 0 @db.message@ @en@ 268445728 @ clients -- Display list of clients workspaces -- synonym for 'clients' p4 clients [ -u user ] [ -e nameFilter -m max ] Reports the list of all clients currently known to the system. The -u user flag limits clients to those owned by the named user. The -e nameFilter flag limits output to clients whose name matches the nameFilter pattern, e.g. -e 'svr-dev-rel*' The -m max flag limits output to the first 'max' number of clients. @ @pv@ 0 @db.message@ @en@ 268445806 @ stream -- Create, delete, modify a stream (unsupported) p4 stream name p4 stream -d name p4 stream -o name p4 stream -i The stream specification form contains the following fields: Stream: Identifies a unique name of the stream as well as its location in the repository (read only). Parent: The parent of this stream. Mainlines have no parent stream. Default is 'none'. Title: A short descriptive name. Default is the Stream. Owner: The stream owner is a Perforce user, defaults to the user name of the creator of the stream. Update: The date this specification was last changed. Access: The date the stream was last used. Type: The type will modify what actions users may take. 'mainline', 'development', 'release', 'patch', 'task', 'experimental' are examples. Default is 'development'. Options: Flags to change the potential flow behavior. The default option is marked with *. active * Stream can parent other streams; retired Stream cannot parent new streams. Description: An optional description. Stream Views will generate templates for future commands. Paths: TBD Remapped: TBD Ignored:TBD @ @pv@ 0 @db.message@ @en@ 268445807 @ streams -- Display list of streams (unsupported) p4 streams [ -u user -l parent -t type -e nameFilter -m max ] Reports the list of all streams currently known to the system. The -u user flag limits streams to those owned by the named user. The -l parent flag limits streams to those with named parent. The -t type flag limits streams to those of named type. The -e nameFilter flag limits output to streams whose name matches the nameFilter pattern, e.g. -e '*ACE*' The -m max flag limits output to the first 'max' number of streams. @ @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 The first form displays the value of the named counter. The second form sets the counter to the given value. The third form deletes the counter. This usually has the same effect as setting the counter to 0. The -f flag sets or deletes counters used by Perforce, as listed in 'p4 help counters'. Moving the 'change' counter backwards can have very bad results. Despite their name, counters can be any value, not just a number. '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 Reports the list of all counters in use by the server. There are nine counters the server uses directly: change the current change number job the current job number journal the current journal number logger event log index used by 'p4 logger' monitor indicates the server has process monitoring enabled security the server security level traits internal trait lot number used by 'p4 attribute' unicode indicates the server metadata is Unicode (UTF8) upgrade the server database upgrade level Other counters can be created by the 'p4 counter' or 'p4 review' commands. @ @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 (given by the environment variable $P4EDITOR) is invoked. The depot specification form contains the following fields: Depot: The name of the depot. This cannot conflict with any branch, client, or label name. Owner: The user who created this depot. Date: The date this specification was last modified. Description: A short description of the depot (optional). Type: 'local', 'remote', or 'spec'. A 'local' depot (the default) is locally managed by the server and occupies space in the server's root directory. A 'remote' depot is a reference 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) into 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 not other automatic updates such as access times or opened files (for changes). There can be only one 'spec' depot. Address: For remote depots, the $P4PORT (connection address) of the remote server. Suffix: For spec depots, the optional suffix (default '.p4s') for the generated paths. 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 (e.g. depot/...). For remote depots, this path refers to the remote server's namespace (e.g. //depot/...). The -d flag deletes the named depot. If any files exist in the depot they must be removed first with 'p4 obliterate'. The -o flag causes the named depot specification to be written to the standard output. The user's editor is not invoked. The -i flag causes a depot specification to be read from the standard input. The user's editor is not invoked. @ @pv@ 0 @db.message@ @en@ 268445732 @ depots -- Display list of defined depots p4 depots Reports the list of all depots created via the depot command. Depots takes no arguments. @ @pv@ 0 @db.message@ @en@ 268445790 @ sizes -- Display size information for files in the depot p4 sizes [ -a ] [ -s | -z ] [ -b blocksize ] file[revRange] ... List files named or matching wild card specification. Display shows depot file name, revision, file count and file size. If client file names are given as arguments the view mapping is used to list the corresponding depot files. The -a flag includes all revisions within the specific range, rather than just the highest revision in the range. The -b option lets the user supply the blocksize (in bytes). When this option is specified each accumulated filesize is rounded up to the nearest blocksize. The -s option calculates the sum of the filesizes for the supplied file argument. The -z option calculates the sum of the filesizes for the supplied file argument, omitting lazy copies. @ @pv@ 0 @db.message@ @en@ 268445733 @ delete -- Open an existing file to delete it from the depot p4 delete [ -c changelist# ] [ -n -v ] file ... Opens a file that currently exists in the depot for deletion. If the file is present on the client it is removed. If a pending changelist number is given with the -c flag the opened file is associated with that changelist, otherwise it is associated with the 'default' pending changelist. Files that are deleted generally do not appear on the have list. The -n flag displays what would be opened for delete without actually changing any files or metadata. The -v flag allows deleting of files that are not synced into the client workspace@ @pv@ 0 @db.message@ @en@ 268445734 @ describe -- Display a changelist description p4 describe [ -d -s -S ] 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 flagged as 'pending' and file diffs are not displayed. 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 (unified), -db (ignore whitespace changes), -dw (ignore whitespace), -dl (ignore line endings). The optional argument to -dc specifies number of context lines. The -s flag requests a shortened form of describe that doesn't include the diffs of files updated. The -S flag displays files that are shelved for the specified changelist including diffs of those files against their previous depot revision. @ @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] ... ] Run diff (on the client) of a client file against the corresponding revision in the depot. The file is only compared if the file is opened for edit or a revision is provided. See 'p4 help revisions' for help specifying revisions. If no file argument is given, diff all open files. This can be used to view pending changelists. 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 (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 forces a diff for every file, regardless of whether they are opened or if the client has the named revision. This can be used to verify the client contents. The -m max flag limits output to the first 'max' number of files. The -s flag reduces the output of diff to the names of files satisfying one of the following criteria: -sa Opened files that are different from the revision in the depot, or missing. -sb Opened for integrate files that have been resolved but have been modified after being resolved. -sd Unopened files that are missing on the client. -se Unopened files that are different 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 are the same as the revision in the depot. The -t flag forces 'p4 diff' to diff even files with non-text (binary) types. If the environment variable $P4DIFF is set then the named program is used rather than the implementation of diff included in the client. The -d option can be used to pass arguments to the external program. Note that since the -s flag is only implemented internally, any -d option used with the -s is ignored. The environment variable $P4DIFFUNICODE is used instead of $P4DIFF if the file being diffed is of a unicode type and the character set is passed as the first argument to that command. @ @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 ] Run diff (on the server) of two files in the depot. Both files may optionally include a revision specification; the default is to compare the head revision. See 'p4 help revisions' for help specifying revisions. Wildcards may be used, but they must match between file1 and file2. Note if using clients or labels as file arguments they must be preceeded with a file path e.g. //...@@mylabel //...@@yourlabel Diff2 introduces each diff with a header line of the form ==== file1 (type1) - file2 (type2) ==== summary file1 or file2 may be '', meaning that only one of the matched files actually exists at the given revision. The summary is one of: 'identical' - file contents are identical and types are the same, 'types' - file contents are identical but the types are different, and 'content' - file contents are different. The -b flag causes diff2 to use the branch view to specify the pairs of files to compare. If file arguments are also present, they can further limit the files and specify the revisions for comparison. Note that if only one file is given, it restricts the right-hand side of the branch view. 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 (unified), -db (ignore whitespace changes), -dw (ignore whitespace), -dl (ignore line endings). The optional argument to -dc specifies number of context lines. The -q suppresses the display of the header lines of files whose content and types are identical and suppresses the actual diff for all files. The -t flag forces 'p4 diff2' to diff even files with non-text (binary) types. The -u flag comes one step closer to patch-friendly output: it uses the GNU diff -u format and displays only files that differ. The file names and dates are in Perforce syntax, but the output seems digestible by the ubiquitous patch program. @ @pv@ 0 @db.message@ @en@ 268445737 @ dirs -- List subdirectories of a given depot directory p4 dirs [ -C -D -H ] dir[revRange] ... List any directories matching the file pattern dir. Because of implementation details, 'p4 dirs' does not allow the ... wildcard. Use the * wildcard instead. Perforce does not track directories per se, but instead considers a path a directory if there are any undeleted files with that path as a prefix. If the dir argument includes a revision range, then only directories with files of those revisions are listed. Normally directories with any files are listed. See 'p4 help revisions' for help specifying revisions. The -C flag limits the output to directories that are mapped on the current client. The -D includes directories with only deleted files. The -H flag lists directories of files on the 'have' list. @ @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 into 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 notes that the current user on the current client has the file opened, and then changes the file permission from read-only to read/write. If -c changelist# is given, the file is put into the pending changelist; the changelist must have been previously created by 'p4 change'. Otherwise the file is opened in the 'default' (unnumbered) changelist. If -t filetype is given, the file is opened as that filetype. Otherwise, the filetype of the previous revision is reused. If the filetype given by -t is a partial filetype, that partial filetype is combined with the previous revision's filetype. See 'p4 help filetypes'. The -n flag displays what would be opened for edit without actually changing any files or metadata. The -k flag bypasses the client file update. It can be used to tell the server that files in a client workspace are already editable, even if they are not present in the client view. Typically this flag is used to correct the Perforce server when it is wrong about the state of files on the client, use of this option can confuse the server if you are wrong about the client's contents. @ @mx@ 2596 1262975099 @pv@ 0 @db.message@ @en@ 268445739 @ files -- List files in the depot p4 files [ -a ] file[revRange] ... List files named or matching wild card specification. Display shows depot file name, revision, file type, change action and changelist number of the current head revision. If client file names are given as arguments the view mapping is used to list the corresponding depot files. If the file argument has a revision, then all files as of that revision are listed. If the file argument has a revision range, then only files selected by that revision range are listed, and the highest revision in the range is used for each file. Normally, the head revision is listed. See 'p4 help revisions' for help specifying revisions. The -a flag displays all revisions within the specific range, rather than just the highest revision in the range. @ @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 files named, working backwards from the latest revision to the first. If the file specification includes a revision, the command limits its output to revisions at or previous to the given revision The -c changelist# flag instructs filelog to display only files submitted at the given changelist number. The -i flag causes inherited file history to be displayed as well. That is, 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 displayed regardless of -i. The -h flag causes filelog to display file content history instead of file name history. The revisions that are listed include those 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 not displayed, even if they are in the history of the specified revision. The -t flag displays the time as well as the date. The -l flag produces long output with the full text of the changelist descriptions. The -L flag produces long output with the full text of the changelist descriptions truncated to 250 characters. The -m maxRevs displays at most 'maxRevs' revisions per file of the file[rev] argument specified. The -s flag requests a shortened form of filelog that doesn't include non-contributory integrations. @ @pv@ 0 @db.message@ @en@ 268445741 @ fix -- Mark jobs as being fixed by a changelist number p4 fix [ -d ] [ -s status ] -c changelist# jobName ... 'p4 fix' marks each named job as being fixed by the changelist number given with -c. The changelist may be either pending or, submitted and the jobs may be still be opened or already 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 will be marked closed when the changelist is submitted. If the job is already closed, it is left alone. The -d flag causes the specified fixes to be deleted. This does not otherwise affect the named changelist or jobs. The -s flag uses the given status instead of the default given with 'p4 jobspec'. This status is reported by 'p4 fixes'. '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 'none', the job's status is left unchanged. @ @pv@ 0 @db.message@ @en@ 268445742 @ fixes -- List what changelists fix what jobs p4 fixes [ -i -m max -c changelist# -j jobName ] [ file[revRange] ... ] 'p4 fixes' shows all jobs with fix records associated with them, along with the changelist number of the fix. Fix records are created either directly with the 'p4 fix' command or via changelist creation with the 'p4 change' and 'p4 submit' commands. The 'p4 fixes' command shows fixes regardless of whether the changelists are submitted or still pending. By default, 'p4 fixes' lists all fixes. This list can be limited in any of three ways. If -j jobName is given, only fixes for the named job are listed. If -c changelist# is given, only fixes from the numbered changelist are listed. If a file (pattern) is given, only fixes for submitted changelists affecting that file (or set of files) are listed. The file pattern may include wildcards and/or a revision number range. See 'p4 help revisions' for help specifying revisions. The -i flag also includes any fixes made by changelists integrated into the specified files. The -m max flag limits output to the first 'max' 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 is intended for programmatic interfaces into Perforce. It dumps information about each file, with each item of information on a separate line. Fstat is best used within a Perforce API application where the items can be accessed as variables, but its output is also suitable for parsing from the client command output. 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 filter flag limits the output to files satisfying the expression given as 'filter'. This filter expression is similar to the one used by 'jobs -e jobview', except that fields must match those above and are case sensitive. e.g. -Ol -F "fileSize > 1000000 & headType=text" Note: the filtering takes place post-compute phase, there are no indexes to optimize performance. The -T fields flag limits the fields output to those specified by a list given as 'fields'. These field names can be separated by a space or a comma and must match those above. e.g. -Ol -T "depotFile, fileSize" The -m max flag limits output to the first 'max' number of files. The -r flag sorts the output in reverse order. The -c changelist# flag instructs fstat to display only files affected since the given changelist number. This operation is much faster than using a revision range on the affected files. The -e changelist# flag instructs fstat to display only files affected by the given changelist number. When used with the -Ro flag, only pending changes will be considered; this is so that files opened for add will also be included. This option will also display the change description. The -O option generates ancilliary output: -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 through the client view -Rh files synced to the client -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 are also supported: -C (-Rc) -H (-Rh) -W (-Ro) -P (-Op) -l (-Ol) -s (-Os). @ @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 new user group or add/delete members from an existing group. A group's members can be users and/or other groups (subgroups). The group specification form is put into a temporary file and the editor (given 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 data size or lock time for operations that the users in that group can perform. 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 represents the time (in seconds) of how long a 'p4 login' ticket remains valid. Note 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. The -d flag deletes all users and groups from the named group, thus deleting the whole group. The -o flag causes the named group specification to be written to the standard output. The user's editor is not invoked. The -i flag causes a group specification to be read from the standard input. The user's editor is not invoked. The new group specification entirely replaces the previous. The -a flag allows a user without 'super' access to modify the group only 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 ] ] ] Displays the list of all user groups defined in the system. If a user argument is given, only groups containing that user are displayed. If a group argument is given, only groups containing the named group are displayed. The -i flag also displays groups that the user or group belongs to indirectly via subgroups. The -m max flag limits output to the first 'max' number of groups. The -v flag displays the MaxResults, MaxScanRows, MaxLockTime, and Timeout values for the named group. @ @pv@ 0 @db.message@ @en@ 268445747 @ have -- List revisions last synced p4 have [ file ... ] List revisions of named files that were last synced from the depot. If no file name is given list all files synced on this client. The format is depot-file#revision - client-file @ @pv@ 0 @db.message@ @en@ 268445748 @ help -- Print help message p4 help [ command ... ] Print a help message about command. If no command name is given print a general help message about Perforce and give a list of 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 a hook into the search engine used by 'p4 jobs -e expr'. It reads its standard input for text, breaks the text into words, and adds those words into 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 given, 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 -- Print out client/server information p4 info Info dumps out what the server knows about the client (the user name, the client name, the applicable client root, the client current directory, and the client IP address) and some server information (the server IP address, server root, date, uptime, version and license data). @ @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' stages change propagation from source files to target files, opening the target files in the client workspace. '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 integration history between files. This eliminates duplicate integrations and minimizes file merges by telling 'p4 resolve' what to use as the merge base: generally the highest revision already integrated. Integration history also prevents integrating back a pure, integration-only change. Such a change is one that resulted from 'p4 resolve' without manually editing the file. The search for integration history will include integrations indirectly through intermediate file branches The commands 'p4 integrated' and 'p4 filelog' display integration history. A branch view may be given directly on the command line by stating the source (from) and target (to) files, or indirectly by naming a stored branch view with -b branch. A stored branch view may have many mappings, while a view on the command line can only have one. If a stored branch view is given, the target files and source files and revisions may be further limited on the command. If no file specification is given then the entire branch view is examined for needed integrations. If a file specification is given, the integration is limited to only those target files. In both cases, the integration is also limited to those target files that are also in the client view. If no revision specification is given then all revisions of the source file are considered for integration. If a single revision is given, then only revisions up to the given revision are included. If a pair of revisions is given (separated by a comma (,)) then only those revisions, inclusively, are integrated. Note that the revision specification concerns the fromFile, but is attached to the toFile. See 'p4 help revisions' for help specifying revisions. The -f flag forces integrate to act without regard for previous integration history. Normally, integrate skips any file revisions already integrated. Note: unless revRange is given as well, the -f flag will force 'p4 resolve' perform merges without a common base. To avoid this, use -f only to force integration of specific changes. If -c changelist# is given, the files are opened in the 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. -d sets -Dt -Ds -Di. -Dt If the target file has been deleted and the source file has changed, will 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, will delete the target file. -Di If the source file has been deleted and re-added, will attempt to integrate all outstanding revisions of the file, including those revisions prior to the delete. Normally 'p4 integrate' only considers revisions since the last add. The -h flag causes the target files to be left at the revision currently on the client (the '#have' revision). Normally, target files are automatically synced to the head revision by 'p4 integrate'. [Note that prior to 2002.1 files were never automatically synced by 'p4 integrate'.] The -i flag enables integration between files that have no integration history. Normally, 'p4 integrate' refuses to integrate changes if there is no prior integration history between the source and target, because it has no way of identifying the base for its merges. The -i flag forces baseless merges and tells 'p4 resolve' just to use the first, added revision as the base. The -o flag displays the base file name and revision which will be used in subsequent resolves if a resolve is needed. The -n flag displays what integrations would be necessary but does not schedule them. 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 whose 'from' files match fromFile[revRange]. If any toFiles are given, the scope is further limited to integrations whose 'to' files match them. When the -s fromFile[revRange] flag is used, -r is ignored, as are any revisions on toFile. [The -s flag is not meant for end users. It exists to support graphical client programs.] The -t flag makes the source file's filetype propagate to the target file. Normally, the target file retain its previous filetype. Newly branched files always use the source file's filetype. The filetype can still be changed before 'p4 submit' with 'p4 reopen'. The -v flag makes 'p4 integrate' work faster by not copying newly branched files to the client. In this case, the files can be fetched with 'p4 sync' after they are submitted with 'submit'. [Note that this was the default behavior for newly branched files in release 97.2 and earlier.] Note: the syntax 'p4 integrate -b branch toFile[revRange]' is provided for backwards compatibility, but is confusing because it mixes the target file with the source revisions. @ @mx@ 2596 1262975099 @pv@ 0 @db.message@ @en@ 268445751 @ integrated -- Show integrations that have been submitted p4 integrated [ -r ] [ -b branch ] [ file ... ] Integrated shows integrations that have already been submitted. Use 'p4 resolve -n' to see unresolved integrations and 'p4 resolved' to see resolved but unsubmitted integrations. If the -b branch flag is given, only files integrated from the source to target files in the branch view are shown. Qualified files are displayed even if they were integrated without using the branch view itself. 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. @ @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 ] 'p4 job' 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 can associate changelists with jobs. With no arguments, 'p4 job' creates a blank job specification form and invokes the user's editor. When the form is saved, a job name of the form jobNNNNNN is created. If a jobName is given on the command line either that named job will be created or, if the job already exists, the job can be modified. As jobs are entered or updated, all fields are indexed for searching by 'p4 jobs'. Text fields are broken into individual alphanumeric words (punctuation and whitespace are ignored) and each word is entered, case folded, 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 of a job are defined by the 'p4 jobspec' command. There is a simple default jobspec that is used if no explicit one has been defined. The -d flag deletes the named job, but only if it has no no pending or submitted fixes associated with it. The -o flag causes the named job specification to be written to the standard output. The user's editor is not invoked. The -i flag causes a job specification to be read from the standard input. The user's editor is not invoked. The -f flag allows otherwise read-only fields to be set. The -f flag requires 'admin' access granted by 'p4 protect'. @ @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 reports which changes have not yet been integrated from a set of source files to a set of target files. The -f option will show the individual files that would require integration. Note that for partially integrated changes, files may be listed even if they have already been integrated individually. The -l flag produces long output with 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 Reports the list of all jobs currently known to the system. If a file (pattern) is given, only fixes for submitted changelists affecting that file (or set of files) are listed. The file pattern may include wildcards and/or a revision number range. See 'p4 help revisions' for help specifying revisions. The -e jobview limits the output to jobs satisfying the expression given as 'jobview'. See 'p4 help jobview' for a description of jobview syntax. The -i flag also 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; this 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 those 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: textual comments 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 '#'. Certain field codes have special significance: 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. Any missing fields simply will not appear in the summary line. If field 105 is present, it is assumed to be a description, which is used by 'p4 change' and 'p4 submit' to annotate the list of jobs to be fixed by the change being created. When updating the jobspec after jobs have been entered, certain limitations apply: Data is stored according to its code. Fields can be renamed by keeping the same code. Removing a code can abandon the associated data stored for the code. Changing the definition of a code (e.g. from 'text' to 'word') can require users to bring jobs into the new format as they are edited. The -o flag causes the job template to be written to the standard output. The user's editor is not invoked. The -i flag causes a job template to be read from the standard input. The user's editor is not invoked. 'p4 jobspec' requires 'admin' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445755 @ label -- Create or edit a label specification and its view p4 label [ -f -t template ] name p4 label -d [ -f ] name p4 label -o [ -t template ] name p4 label -i [ -f ] Create a new label specification or edit an existing label specification. A name is required. The specification form is put into a temporary file and the editor (given 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 this specification was last modified. Access: The date of the last 'labelsync' or use of '@@label' on this label. Description: A short description of the label (optional). Options: Flags to change the label behavior. locked Allows only the label owner to change its specification. Prevents the label from being deleted. Prohibits 'p4 labelsync'. Revision: An optional revision specification for an automatic label. Note that this field must be quoted if it contains the # (form comment) character. View: A mapping to select files from the depot. The default view selects all depot files. See 'p4 help views', but note that only the left hand side of a mapping is used for labels. A label is a shorthand for referring to a collection of revisions. See 'p4 help revisions' for information on using labels. 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 associated with the label by the 'p4 tag' or 'p4 labelsync' commands. A static label cannot have a Revision: field. Flag -d causes the named label to be deleted, as long as it is not locked. The -f flag forces the delete. The -o flag causes the named label specification to be written to the standard output. The user's editor is not invoked. The -i flag causes a label specification to be read from the standard input. The user's editor is not invoked. The -t flag constructs the label's view by copying the named template label's view, instead of using the existing view or creating a new default view. It also copies the label options from the template label. The -f flag can force the deletion of a label; normally locked labels can only be deleted by their owner. -f also allows the last modified date to be set. The -f flag requires 'admin' access 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] ] Reports the list of all labels currently known to the system. If files are specified, 'p4 labels' limits its report to labels that contain those files. Note that when a file specification is given no automatic labels will be displayed. If the file specification includes a revision range, 'p4 labels' limits its report to labels that contain those particular revisions. See 'p4 help revisions for help specifying revisions. The -t flag displays the time as well as the date. The -u user flag limits labels to those owned by the named user. The -e nameFilter flag limits output to labels whose name matches the nameFilter pattern, e.g. -e 'svr-dev-rel*' The -m max flag limits output to the first 'max' number of labels. @ @pv@ 0 @db.message@ @en@ 268445757 @ labelsync -- Synchronize label with the current client contents p4 labelsync [ -a -d -n ] -l label [ file[revRange] ... ] Labelsync causes the named label to reflect the current contents of the client. It records the last revision of each file taken onto the client. 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 given, labelsync updates only that named file. If the file argument includes a revision specification, then that revision is used instead of the revision taken by the client. If the revision specified is a deleted revision, then the label will include that deleted revision. See 'p4 help revisions' for help specifying revisions. If the file argument includes a revision range specification, then only files selected by the revision range are updated, and the highest revision in the range is used. The -a flag causes labelsync to add the named file to the label; no files will be deleted from the label. The -d deletes the named file from the label, regardless of revision. The -n flag lists how the label would be affected, but doesn't actually update the label. Only the owner of a label may run labelsync on that label. A label that has its Options: set to 'locked' cannot be updated. @ @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 that there is already 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 shutdown the server and manually copy the license file in place. Most new license files obtained from Perforce can be installed with this command, except for when the IPAddress has changed. In that case the server will have to be stopped and restarted after the new license file has been manually copied. The -o flag causes the license file to be written to the standard output. The -i flag causes a new license file to be read from the standard input. This command requires 'super' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445758 @ lock -- Lock an opened file against changelist submission p4 lock [ -c changelist# ] [ file ... ] The open files named 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 then the lock request is rejected. If no file names are given then lock all files currently open in the changelist number given or in the 'default' changelist if no changelist number is given. @ @pv@ 0 @db.message@ @en@ 268445759 @ logger -- Report what jobs and changelists have changed 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) with 'p4 counter'. Each event has a sequence number. The presence of an entry in the log doesn't guarantee that the named entity has changed. If a sequence# is given with -c, only events since that number are listed. If a counter is given with -t, only events since the number of that counter are listed. If both are given, then 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. This generally means that only one user can really make use of this option. 'p4 logger' is not meant as an end-user command. It exists to support propagating information to an external defect tracking system. 'p4 logger -c' requires 'review' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445785 @ login -- Login to Perforce by obtaining a session ticket p4 login [ -a -p ] [ user ] p4 login [ -s ] The login command allows a user to access Perforce until either the session expires or the user issues a 'logout' command. When a user "logs in" to Perforce they are prompted for the users password, if they supply this correctly then they are issued with a ticket. The ticket issued will expire after the default timeout value has been reached and is only good for the host machine that the 'login' command was executed from (see below for exception). The ticket can be used anywhere that a password can be used. e.g. p4 -P changes -m1 The -a flag causes the server to issue a ticket which is valid on all host machines. The -p flag just displays the ticket rather than storing it on the client machine. The -s flag shows the status of the current ticket (if there is one). Requesting a login of someone other than the current user requires 'super' access granted by 'p4 protect'. In this case 'p4 login' does not prompt for the users password. @ @mx@ 2596 1262975099 @pv@ 0 @db.message@ @en@ 268445786 @ logout -- Logout of Perforce by removing or invalidating a ticket. p4 logout [-a] The logout command will remove the ticket on the client, the user will have to issue another 'p4 login' to continue use. The -a flag causes the ticket on the server to be invalidated, this will logout all users of that ticket from Perforce. @ @pv@ 0 @db.message@ @en@ 268445794 @ merge3 -- 3-way file merge (unsupported) p4 merge3 [ -db -dw -r -t -v ] base leg1 leg2 Performs a 3-way merge of the named files and writes the results on standard output. This is the only command besides 'p4 set' that is implemented on the client, and thus the file names are strictly local. The intent of merge3 is to drive graphical merge tools. -db, -dw, -t, and -v are the same as in 'p4 resolve'. -r changes 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 is an admin utility that allows the user to see what current p4 processes are running. Monitor tracks the Perforce processes in a special table, this table is constantly being updated so there is a potential minor performance impact. To make use of this command it is required that 'monitoring' be enabled through the monitor counter. 'p4 monitor show' displays current process information; for each process the process-id, status (Running/Terminate), owner, command are listed per line of output. 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 shown. The -l flag produces long output with the full username and full argument list. 'p4 monitor terminate [id]' marks the command specified by its 'id' for termination. This command requires 'super' access. 'p4 monitor clear [id|all]' removes the process record specified by its 'id' from the monitor table. All of the records are removed if the option 'all' is supplied instead of an 'id'. This may 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# ] [ -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 opened 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 may 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' will both undo the move and revert the unsubmitted content. If -c changelist# is given, the file will be reopened in the specified pending changelist as it is moved. If -t filetype is given, the file is reopened as that filetype. If the filetype given by -t is a partial filetype, that partial filetype is combined with the current filetype. See 'p4 help filetypes'. The -n flag lists the moves which would be performed without actually doing them. The -k flag bypasses the client file rename. It can be used to tell the server that the user has renamed a file on the client. The use of this option can confuse the server if you are wrong about the client's contents. Note that the 'move' command requires a release 2009.1 or newer 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 removes files and their history from the server in a way that they won't come back. (See 'p4 delete' for the non- destructive way to delete a file.) It retrieves space used by those files in the archive and then clears the files from all lists maintained by the server. Files in client workspaces are not affected, except that Perforce will no longer recognize them as being under its control. Obliterate is aware of lazy copies made when 'p4 integrate' creates a branch, and will not remove copies 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, then only that revision is obliterated. If the file argument has a revision range, then only the revisions in that range are obliterated. See 'p4 help revisions' for help. The -y flag instructs obliterate to do its work. Otherwise, it just displays what it would do. 'p4 obliterate' requires 'admin' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445761 @ opened -- Display list of files opened for pending changelist p4 opened [ -a -c changelist# -C client -u users -m max ] [ file ... ] Lists files currently opened in pending changelists, or indicates for the specified files whether they are currently opened and/or locked. If no file names are given, all files open in the current client workspace are listed. The -a flag lists opened files in all clients. Normally only files opened by the current client are listed. The -c changelist# flag restricts the list to files opened under the given changelist#. Normally files in any changelist (include the 'default') are listed. The -C client flag restricts the list of files to those opened on the named client. The -u user flag restricts the list of files to those opened by the named 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. Once a password is set for a user on the server, then in order for that user to invoke any Perforce client commands the same password must be set on the client in the environment variable $P4PASSWD. (On Windows, 'p4 passwd' sets this as well.) 'p4 passwd' prompts for both the old password and the new password with character echoing turned off. Setting the password to an empty string deletes the password. The -O flag provides the old password, avoiding prompting. The -P flag provides the new password, avoiding prompting. Setting the password of someone other than the current user requires 'super' access granted by 'p4 protect'. In this case 'p4 passwd' does not prompt for the old password. @ @pv@ 0 @db.message@ @en@ 268445763 @ print -- Retrieve a depot file to the standard output p4 print [ -a -o localFile -q ] file[revRange] ... Retrieve the contents of a depot file to the client's standard output. The client's have list is not affected. If file is specified as a client file name, the client view is used to find the corresponding depot file. If the file argument has a revision, then all files as of that revision are 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 used for each file. Normally, the head revision is printed. See 'p4 help revisions' for help specifying revisions. The -a flag prints all revisions within the specific range, rather than just the highest revision in the range. The -o localFile flag redirects the output to the named file on the client filesystem. In this case, at most one file is written. 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 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. Note: remote depot accesses are made using the pseudo-user 'remote'; access by other servers can be controlled by granting 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 right only includes the specific right and not all the lesser rights. This makes it possible to deny individual rights without having to then re-grant lesser rights. Modes prefixed by '=' are rights; all other modes are permission 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 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 - allows 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: 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 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 supplied in the first field. The -o flag causes the protection table to be written to the standard output. The user's editor is not invoked. The -i flag causes the protection table to be read from the standard input. The user's editor is not invoked. Once protections are in place, 'p4 protect' requires 'super' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445789 @ protects -- Display protections in place for a given user/path p4 protects [ -a | -g group | -u user ] [ -h host -m ] [ file ... ] 'p4 protects' display the lines from the protections table that apply to the current user. The protections table is managed by 'p4 protect'. If the -a flag is given, protection lines for all users are displayed. If the -g group flag or -u user flag is given, protection lines for that group or user are displayed. If the -h host flag is given, only those protection lines that apply to the given 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 does not take exclusions into account. If the file argument is given, only those protection lines that apply to the named 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 Use 'p4 move' to move or rename files. Note that Perforce clients prior to release 2009.1 do not support 'p4 move'. However, files in older clients can be effectively renamed by branching one file into another and then 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 that files renamed in this way will be treated as branched files rather than moved files in subsequent operations. @ @pv@ 0 @db.message@ @en@ 268445766 @ reopen -- Change the type or changelist number of an opened file p4 reopen [ -c changelist# ] [ -t filetype ] file ... Reopen takes an already opened file and reopens it for the current user, optionally changing its changelist or filetype. The changelist must have previously been created with 'p4 change' or may be the 'default' changelist. If -t filetype is given, the file is reopened as that filetype. If the filetype given by -t is a partial filetype, that partial filetype is combined with the current filetype. 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 open in the client workspace, using an interactive dialog. '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'. Once scheduled, 'p4 resolve' must perform the merges before the file can be committed with 'p4 submit'. If no file is given, all files needing merging will be resolved. The merge process is a classic 3-way merge, with the participating files named (for better or for worse): 'yours' -- the target file open in the client workspace; 'theirs' -- the source file being merged from the depot; and 'base' -- the common ancestor, actually 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 will have 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 textual resolution. The 'merge' option allows you to invoke your own integration and conflict resolution utility (named in the $P4MERGE environment variable). This utility is expected to 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 (e.g. binary files) are always 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 can be used to handle 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 which modify the diff output but do not modify merge behavior include -dn (RCS), -dc (context), -ds (summary), and -du (unified). Note that 'p4 resolve' will use text from the client file where the files differ only in whitespace. The -f flag allows previously resolved files to be resolved again. Normally, once files have been resolved then 'p4 resolve' won't display them again. The -n flag lists the merges which would be performed without actually doing them. The -o flag displays the base file name and revision which will 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 put in markers for all changes, not just those in conflict. The markers must be edited out before the merged file can be accepted. @ @mx@ 2596 1262975099 @pv@ 0 @db.message@ @en@ 268445768 @ resolved -- Show files that have been merged but not submitted p4 resolved [ -o ] [ file ... ] Resolved shows integrations that have already been resolved but not yet submitted. Use 'p4 resolve -n' to see unresolved integrations and 'p4 integrated' to see already submitted integrations. The -o flag reports the revision used as the base during the resolve. @ @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 type given as '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 displays what revisions would be changed but does not actually change them. 'p4 retype' ignores files from remote depots. 'p4 retype' will not purge older revisions when a filetype is retyped to a '+Sn' type, only subsequent edits will cause revisions to be purged. 'p4 retype' requires 'admin' access granted by 'p4 protect'. 'p4 retype' is unsupported, due to the fact that it cannot be 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 back to the revision previously synced from the depot, discarding any pending changelists or integrations that have been made. This command requires naming files explicitly. After running revert the named files will no longer be locked or open. The -a flag tells 'p4 revert' to revert only those files which are opened for edit or integrate and are unchanged or missing. Files with pending integration records are left open. With the -a flag, the file arguments are optional. The -n flag displays what files would be affected but does not actually revert them. The -k flag bypasses the client file refresh. It can be used to make the server believe the file is no longer open, but keeps the file unchanged in the client workspace. The -c flag limits 'p4 revert' to files opened under the given, pending 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 named counter. If the counter is not given, 'p4 review' lists all changelists. (If a changelist# and counter are given, '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 -- Show what users are subscribed to review files p4 reviews [ -c changelist# ] [ file ... ] 'p4 reviews' lists all users who have subscribed to review the named files, the files in the numbered changelist, or all files by default. Users subscribe to review files via the 'p4 user' command. @ @pv@ 0 @db.message@ @en@ 268445796 @ search -- Search index (unsupported) p4 search words Search is a hook into the search engine used by 'p4 jobs -e expr'. It searches the index for the given words and dumps out any keys with those words as values. 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 will scan the specified file revisions for any revision whose archive file (revision contents) is a lazy copy. For each of these files the contents will be copied into that revisions archive namespace. This will increase the overall amount of space required for the archive but will ensure that (manually) deleting any other part of the archive will not affect the named revisions. If a second file argument is supplied to snap, then only lazy copies with content in the named archivePath will be copied. The -n flag displays what files would be snapped without actually copying any files or changing any metadata. 'p4 snap' requires 'admin' access 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 the registry variables used by Perforce on Windows platforms. Normally, the variable 'var' is set to 'value'. If 'value' is missing, the variable 'var' is unset. Without any arguments at all, 'p4 set' list variable settings. The -s flag causes 'p4 set' to set variables for the whole system rather than for the user. You must have NT administrator powers to use this. The -S service flag causes 'p4 set' to set variables for the named service. You must have NT administrator powers to use this. Currently, registry variable entries may 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 persist 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 into the depot. The user is presented with a changelist form in the user's text editor that is configured for editing Perforce specifications. If a file pattern is specified, 'p4 shelve' limits the list of files to those matching the pattern. The -i flag causes the pending changelist specification with shelved files to be read from the standard input. The user's editor is not invoked. This option implies -c when used to modify an existing changelist with shelved files. 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 is allowed to add or modify its shelved files. The -f flag must be used with the -c or -i flag to force overwriting 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 is allowed to 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 is allowed to delete its shelved files. Any user with 'admin' access may use -d with the -f flag to force deleting shelved files. @ @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 ] files p4 submit [ -r -f option ] -d description p4 submit [ -r -f option ] -d description files 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. With no argument 'p4 submit' attempts to submit all files in the 'default' changelist. Submit provides the user with a dialog similar to 'p4 change' so the user can compose a changelist description. In this dialog the user is presented with the list of files open in changelist 'default'. Files may be deleted from this list but they cannot be added. (Use an open command (edit, add, delete) to add additional files to a changelist.) If a (single) file pattern is given, only those files in the 'default' changelist that match the pattern will be submitted. The -c flag submits the numbered pending changelist that has been previously created with 'p4 change' or a failed 'p4 submit'. The -d flag allows a description to be passed into submit rather than using a numbered changelist or engaging in a change description dialog. This option is useful when scripting but does not allow for jobs to be added or the default changelist to be modified. The -f flag allows a submit option to be passed into submit which will override the one that is set in the client. See 'p4 help client' for valid submit options. The -i flag causes a changelist specification (including files to be submitted) to be read from the standard input. The user's editor is not invoked. The -r flag allows submitted files to remain open (on the client's default changelist) after the submit has completed. 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 more notes on this option. Before committing a changelist submit locks all associated files not already locked. If any file cannot be locked, or if the submit fails for any other reason the files are left open in a newly created pending changelist. Submit is guaranteed to be atomic. Either all files will be updated in the depot as a unit or none will be. @ @pv@ 0 @db.message@ @en@ 268445795 @ spec -- Edit spec definitions (unsupported) p4 spec [ -d -i -o ] type Spec edits any of the spec definitions: branch, change, client, depot, group, job, label, spec, trigger, typemap, user. Very little can be changed: only the comments and the formatting hints. Adding fields is possible, but there is no storage to hold them, and so their contents disappear when 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 ] [ file[revRange] ... ] p4 sync [ -n -p ] [ 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 is used to map client file names to depot file names and vice versa. Sync adds files that are in the client view but which have not been retrieved before. Sync deletes previously retrieved files which are no longer in the client view or have been deleted from the depot. Sync updates files which are still in the client view and which have been updated in the depot. Normally, sync affects all files in the client workspace. If file arguments are given, sync limits its operation to those files. The file arguments may 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, then only files selected by the revision range are updated, and the highest revision in the range is used. Normally, sync will not clobber files in the client workspace that the user has made writable. Setting the 'clobber' option in the client spec disables this safety check. The -f flag forces resynchronization even if the client already has the file, and clobbers writable files. This flag doesn't affect open files. The -n flag causes sync not to update the client workspace, but to display what normally would be updated. The -k flag bypasses the client file update. It can be used to make the server believe that a client workspace already has the file. Typically this flag is used to correct the Perforce server when it is wrong about what files are on the client, use of this option can confuse the server if you are wrong about the client's contents. 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 requirement of saving the client workspace state. @ @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 indicated by the file argument. Once 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 will be 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 will be tagged. Files with more than one revision in the range will be tagged at the highest revision. The -d deletes the association between the specified files and the label, regardless of revision. The -n flag lists the files that would be tagged, but doesn't actually do anything. Tag can be used with an existing label (see 'p4 help labels') or with a new one. An existing label may be used only by its owner, but 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 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 either before the file transfer, between file transfer and changelist commit, or after the commit. Manipulate and validate forms. The server runs form-validating triggers either 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 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 may 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: 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' as well as by '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 for expansion on the job 'form-commit' trigger command line. form-delete: Execute form trigger prior to delete of form after its contents are parsed. Path: For change triggers, a file pattern to match files in the changelist. This file pattern may 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 may 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, the whole command must be quoted. 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, 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 causes the trigger table to be written to the standard output. The user's editor is not invoked. The -i flag causes the trigger table to be read from the standard input. The user's editor is not invoked. 'p4 triggers' requires 'super' access granted by 'p4 protect'. @ @mx@ 2596 1262975099 @pv@ 0 @db.message@ @en@ 268445777 @ typemap -- Modify the file name-to-type mapping table p4 typemap p4 typemap -o p4 typemap -i 'p4 typemap' edits a name-to-type mapping table for 'p4 add', which consults the table to select a file's filetype based on its name. The typemap form has a single entry '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. This is a file pattern and may be an exclusion mapping (-pattern) to exclude files. Note to match all files anywhere in the depot hierarchy, the pattern must begin with //..., and to match any file with a given suffix you must either specify '//.../*.suffix' or '//....suffix' (four dots). As with all mappings, later entries override earlier entries. If no matching entry is found in the table, 'p4 add' senses the file's filetype by examining the file's contents and execution permission bits. The -o flag causes the typemap table to be written to the standard output. The user's editor is not invoked. The -i flag causes the typemap table to be read from the standard input. The user's editor is not invoked. 'p4 typemap' requires 'admin' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445778 @ unlock -- Release a locked file but leave it open p4 unlock [ -c changelist# ] [ -f ] [ file ... ] 'p4 unlock' releases a lock on an open file in a pending changelist. If the file is open in a specific pending changelist other than 'default', then the -c flag is required to specify the pending changelist. If no file name is given then all files in the designated changelist are unlocked. The -f flag can unlock any file; normally files can only be unlocked by their owner. The -f flag requires 'admin' access 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 the shelved files from a pending changelist and copies them into a pending changelist on 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' limits the list of files to those matching the pattern. The -c flag specifies the changelist number to receive the shelved files. By default, 'p4 unshelve' opens shelved files into the default changelist. The -f flag forces the clobbering of any writeable but unopened files that are being unshelved. The -n flag previews what would be unshelved without actually 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 (given by the environment variable $P4EDITOR) is invoked. Normally, a user specification is created automatically the first time the user invokes any client command that can update the depot. The 'p4 user' command is generally used to edit the user's reviewing 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 (user@@client default). Update: The date the specification was last modified (read only). Access: The date the user last issued a client command. FullName: The user's real name. JobView: Selects jobs to be presented at changelist creation. These are the jobs that can be closed automatically upon changelist submission. See 'p4 help jobview' for a description of jobview syntax. Reviews: The subscription list for change review. You may use wildcards: ... matches any characters including / * matches any character except / There may be any number of review lines. Password: The user's password. See also 'p4 help passwd'. The -d flag deletes the named user, but only if the user has no opened files. The -o flag causes the named user specification to be written to the standard output. The user's editor is not invoked. The -i flag causes a user specification to be read from the standard input. The user's editor is not invoked. The -f flag can force the creation, update or deletion of any named user, or to change the last modified date. By default, users can only delete or modify their own user specifications. The -f flag requires 'super' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445780 @ users -- Display list of known users p4 users [ user ... ] [ -m max ] Reports the list of all users, or those users matching the argument, currently known to the system. The report includes the last time each user accessed the system. The -m max flag limits output to the first 'max' number of users. @ @pv@ 0 @db.message@ @en@ 268445781 @ verify -- Verify that the server archives are intact p4 verify [ -m maxRevs ] [ -q ] [ -u | -v | -z ] file[revRange] ... 'p4 verify' reports for each revision of the named files the revision specific information and an MD5 digest (fingerprint) 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 (e.g. 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 limits verify to 'max' total revisions. This can be used with the -u flag to compute and save digests in batches. The -u flag causes 'p4 verify' to compute and save the digest for each revision that has no saved digest. Revisions already with saved digests are skipped. The -v flag forces 'p4 verify' to compute and save the digest for each revision, even if it already has a saved digest. This can be used to update the saved digest if the archive was changed deliberately. The -z flag instructs 'p4 verify' to optimize digest computations by skipping revisions which have already been computed in the current pass. This is useful when the named files contain lazy copies. Note that the output may report a lazy copy revision if it is the first revision in the sort order to access a common archive file. This option is not available with the '-v' or '-u' options. The -q flag instructs 'p4 verify' to operate quietly. The only output would be errors from mismatched digests or errors due to unreproducible revisions. The following command will verify all revisions of all archive files: p4 verify -qz //... Saved digests are also used by 'p4 diff' to avoid having to compute them each time. 'p4 verify' requires 'admin' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445782 @ where -- Show how file names map through the client view p4 where [ file ... ] Where shows how the named files map through 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 no file is given, the mapping for '...' (all files in the current directory and below) is shown. Note that 'p4 where' does not determine where any real files are. It only computes where they should be according to the client view. @ @pv@ 0 @db.message@ @en@ 268445801 @ Zeroconf service support The following flags and environment variables apply to both server and proxy processes p4d -0 When the Perforce server is registered as zeroconf service, the service-type is 'p4', visible in browse mode of DNS Service Discovery as '_p4._tcp'. If mDNS is not available on the host, service registration will fail, log an error in the server log and the server will continue the startup process. The -0 (digit zero) flag is used to enable zeroconf registry, at server start time, overriding the value of $P4ZEROCONF in the environment. When using the environment variable, the presence of the variable in the environment enables the service registry. Two additional identity flags complement zeroconf registry. p4d -In name Specify a unique identifiable name for your server. This name is visible from the server with 'p4 -ztag info' output or with DNS Service Discovery, if registering the process as a zeroconf service. Passing the flag -In overrides the value of $P4NAME in the environment. Enclose name in quotes when including spaces. p4d -Id description Specify an identifiable description for your server. This setting is visible from the server with output from 'p4 -ztag info' or with DNS Service Discovery, if registering the process as a zeroconf service. Passing the flag -Id overrides the value of $P4DESCRIPTION in the environment. Enclose description in quotes when including spaces. @ @pv@ 0 @db.message@ @en@ 268445802 @ Perforce server tunables (unsupported) The following server parameters can be tuned, by setting 'tunables' to a list of variable=value pairs separated by commas. Changes to these values should only be made with the guidance of technical support, usually as part of debugging or improving performance of a particular command. Values too large or small are silently adjusted within these limits. 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.bufsize 16K Journal/checkpoint read/write size dbjournal.wordsize 4K Journal word processing size dbopen.cache 64 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.nofsync 0 Disable fsync of db files 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.domain.accessupdate 300 Time interval to update domain access time dm.domain.accessforce 3600 Time interval to force domain access time 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.integ.maxact 100K Max db.integed edges considered for a file dm.isalive 50K Rows scanned befor 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 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 filesys.binaryscan 8K 'add' looks this far for binary chars filesys.bufsize 4K client file I/O buffer size filesys.maketmp 10 max attempts to find unsed 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 lbr.bufsize 4K archive file I/O buffer size map.joinmax1 10K Produce at most map1+map2+joinmax2 map.joinmax2 1M Produce at most joinmax2 net.bufsize 4K network I/O buffer size net.tcpsize 16384 TCP sndbuf/rcvbuf sizes set at connect rcs.maxinsert 50M max lines in RCS archive file rcs.nofsync 0 Disable fsync of RCS files rmt.sendjournal 0 enable journal transmission for replication rpc.himark 2000 max outstanding data between server/client rpc.lowmark 700 interval for checking outstandind data spec.hashbuckets 0 hash spec domains to sub directories @ @pv@ 0 @db.message@ @en@ 268445805 @ dbschema -- Report meta database information p4 dbschema [ tablename[:tableversion] ]... 'p4 dbschema' reports database structure information from 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, alternatively you can restrict output by specifying table names and versions. The results are returned as tagged output. Table names match 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 ] p4 export -j token [ -J prefix ] [ -f ] [ -l lines ] [ -F filter ] p4 export -j token [ -J prefix ] -r '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 changes the output so that non-textual datatypes are formatted 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. Note: Some fields are added to the tagged output to indicate transactional consistency or the end of the journal. Note: The final record reported 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 will be inserted. This tag indicates to a polling process that it should wait for more data before issuing the next export command. Note this final record is not filtered. Note: Journal 'ex' records can have a 'markers' 'complete' tag added. This indicates that, when that transaction ended, there were no known outstanding transactions. Note: Raw journal output has the raw journal text in a 'data' tag. Other tags can indicate positions of transactional complete locations in the journal. @ @mx@ 2596 1262975099 @pv@ 0 @db.message@ @en@ 268445817 @ replicate -- poll for journal changes and apply to another server p4 replicate [ -j token ][ -s statefile ][ -i interval ][ -k -x ] [ -J prefix ][ -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 specifies that the pipe to the sub-process command should remain open across polling intervals. By default, the pipe to the sub-process is restarted for every record batch. The -x flag specifies that 'p4 replicate' should terminate when a journal rotation is detected. The -o output flag specifies an output file where journal records will be written in addition to the sub-process command. See Perforce Knowledge base article 1099 for detailed usage. Super permission is required for all invocations. @ @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 outputs a little histogram showing distances between leaf pages, for the purposes of anticipating disk seeks due to sequential database scans. Dbstat scans only the internal node pages of the file, not the leaf or overflow pages, and thus only reads 1-5%% of the file. However since it locks out write access to the database table during its scan, the command should be used carefully. The -a flag outputs histogram stats for all tables. The -s flag is used to report files size of the database tables. This command requires 'super' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445810 @ logstat -- Report size of journal/errorLog/auditLog files p4 logstat Logstat reports the file size of any existing journal, errorLog and auditLog files. This command requires 'super' access granted by 'p4 protect'. @ @pv@ 0 @db.message@ @en@ 268445811 @ lockstat -- Report lock status of database tables p4 lockstat Lockstat reports any 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 for getting the next block when available. The -s flag option allows the user 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, all blocks from the offset are output until the end of the file. The data is returned in blocks of size blockSize in the tagged field 'data'. 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 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 will be sequential. The -c flag causes dbpack to stop after the specified number of leaf pages have been reordered. The -l flag is a threshold which 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 does all tables. @ @pv@ 0 @db.message@ @en@ 268445814 @ ping -- test network performance (unsupported) p4 ping [ -f ][ -p ][ -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. Typically the round trip time is 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 (in seconds) to transmit. This can be as long as 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; 0 for no pause. This can be as long as 120 seconds. The -s and -r flags specify the size of the message as a positive number. -s specifies the server-to-client message size, up to 10000000 characters -r specifies the client-to server message size up to 100000 characters Be advised that 'p4 ping' can flood the network with traffic. The command requires admin privileges. @ @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@ 857800705 @%operation%: %arg%: %errmsg%@ @pv@ 0 @db.message@ @en@ 857800706 @%operation%: %arg%: unknown errno %errno%@ @pv@ 0 @db.message@ @en@ 858128387 @%operation%: %arg%: %errmsg%@ @pv@ 0 @db.message@ @en@ 858128388 @%operation%: %arg%: unknown network error %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@ 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@ 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!@ @mx@ 2596 1262975099 @pv@ 0 @db.message@ @en@ 807541811 @Some file(s) could not be transferred from client.@ @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@ 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@ 824384832 @Perforce server requires at least "Service Pack 3" for Windows 2000, this machine has only "%pack%".@ @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@ 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@ 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@ 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@ 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@ 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@ 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@ 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 [ -aciq -d ] 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 ] [ -f | -u ] [ changelist# ]@ @pv@ 0 @db.message@ @en@ 805379282 @Usage: change -d [ -f ] changelist#@ @pv@ 0 @db.message@ @en@ 805379283 @Usage: change -o [ -s ] [ changelist# ]@ @pv@ 0 @db.message@ @en@ 805379284 @Usage: change -i [ -s ] [ -f | -u ]@ @pv@ 0 @db.message@ @en@ 805379285 @Usage: changes [-i -t -l -L -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@ 805379290 @Usage: counter [ -df ] counter_name [ value ]@ @pv@ 0 @db.message@ @en@ 805379291 @Usage: counters@ @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] [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] 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@ 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@ @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@ 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] -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#] [ -f -k -n -v ] [-t type] files...@ @pv@ 0 @db.message@ @en@ 805379470 @Usage: add/delete [-c changelist#] [ -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 | -u user ] [ -h host -m ] [ file ... ]@ @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@ 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 | -z ] [ -b blocksize ] 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 -f -i -o -l parent ] [ streamname ]@ @pv@ 0 @db.message@ @en@ 805379456 @Usage: stream -d [ -f ] streamname@ @pv@ 0 @db.message@ @en@ 805379457 @Usage: stream -i [ -f ]@ @pv@ 0 @db.message@ @en@ 805379458 @Usage: stream -o streamname@ @pv@ 0 @db.message@ @en@ 805379459 @Usage: streams [ -u user ] [ -l parent ] [ -t type ] [ -e query ] [ -m max ]@ @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@ 805379349 @Usage: sync [-f -k -n -p] [files...]@ @pv@ 0 @db.message@ @en@ 805379420 @Usage: sync [ -n -p ] [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@ 805379350 @Usage: triggers [ -i | -o ]@ @pv@ 0 @db.message@ @en@ 805379443 @Usage: tunables [ -a ]@ @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 [ -m max ]@ @pv@ 0 @db.message@ @en@ 805379358 @Usage: verify [ -m maxRevs ] [ -q ] [ -u | -v | -z ] files...@ @mx@ 2596 1262975099