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'.
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
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
The following type aliases exist for backwards compatibility:
Type Is Base Type Plus Modifiers
-------- ------------ --------------
ctext text +C
cxtext text +Cx
ktext text +k
kxtext text +kx
ltext text +F
tempobj binary +Sw
ubinary binary +F
uresource resource +F
uxbinary binary +Fx
xbinary binary +x
xltext text +Fx
xtempobj binary +Swx
xtext text +x
'p4 add', 'p4 edit', and 'p4 reopen' can take a '-t filetype'
to specify a file's filetype.
For 'p4 add' the default filetype is set by the file name-to-type
mapping table managed by 'p4 typemap'. If the file name is not
mapped in that table, 'p4 add' senses the filetype by examining
the file's contents and execution permission bits.
For 'p4 edit' and 'p4 reopen' the default filetype is the filetype
of the previous revision.