p4 add opens files within the client workspace for addition to the depot. The specified file(s) are linked to a changelist; the files are not actually added to the depot until the changelist is sent to the server with
p4 submit. The added files must either not already exist in the depot, or exist in the depot but be marked as deleted at the head revision.
To open a file with p4 add, the file must exist in your client workspace
view, but does not need to exist in your workspace at the time of
p4 add. The file must, however, exist in your workspace when you run
p4 submit, or the submission will fail.
p4 add does not create or overwrite files in your workspace; if a file does not exist, you must create it yourself.
By default, the specified files are linked to the default changelist. Use -c to specify a different changelist. (Or use the
p4 change command to move files from the default changelist to a numbered changelist.)
When adding files, Perforce first examines the typemap table (p4 typemap) to see if the system administrator has defined a file type for the file(s) being added. If a match is found, the file's type is set as defined in the typemap table. If a match is
not found, Perforce examines the first 8192 bytes of the file to determine whether it is
text or
binary, and the files are stored in the depot accordingly. By default, text file revisions are stored in reverse delta format; newly-added text files larger than 10MB are assigned filetype
text+C and stored in full. Binary revisions are stored as full files.
To add files containing the characters @,
#,
*, and
%, use the
-f flag. This flag forces literal interpretation of characters otherwise used by Perforce as wildcards.
If you manually expand the @ sign and attempt to add the file
status%40june.txt, Perforce interprets the
% sign literally, expands it to the hex code
%25, resulting in the filename
status%2540june.txt.
