импорт из репозиториев Perforce и отправка в них (Import from and submit to Perforce repositories)
CLIENT SPEC
The p4 client specification is maintained with the p4 client
command and contains among other fields, a View that specifies
how the depot is mapped into the client repository. The clone and
sync commands can consult the client spec when given the
--use-client-spec option or when the useClientSpec variable is
true. After git p4 clone, the useClientSpec variable is
automatically set in the repository configuration file. This
allows future git p4 submit commands to work properly; the submit
command looks only at the variable and does not have a
command-line option.
The full syntax for a p4 view is documented in p4 help views. git
p4 knows only a subset of the view syntax. It understands
multi-line mappings, overlays with +, exclusions with - and
double-quotes around whitespace. Of the possible wildcards, git
p4 only handles ..., and only when it is at the end of the path.
git p4 will complain if it encounters an unhandled wildcard.
Bugs in the implementation of overlap mappings exist. If multiple
depot paths map through overlays to the same location in the
repository, git p4 can choose the wrong one. This is hard to
solve without dedicating a client spec just for git p4.
The name of the client can be given to git p4 in multiple ways.
The variable git-p4.client takes precedence if it exists.
Otherwise, normal p4 mechanisms of determining the client are
used: environment variable P4CLIENT, a file referenced by
P4CONFIG, or the local host name.
