Avoid mapping conflicts
When you use multiple mappings in a single view, a single file can inadvertently be mapped to two different places in the depot or workspace. When two mappings conflict in this way, the later mapping overrides the earlier mapping.
Example: Erroneous mappings that conflict
Joe has constructed a view as follows:
Copy
View:
//Acme/proj1/... //joe/project/...
//Acme/proj2/... //joe/project/...The second mapping //Acme/proj2/... maps to
//joe/project and conflicts with the first mapping.
Because these mappings conflict, the first mapping is ignored; no files
in //Acme/proj1 are mapped into the workspace:
//Acme/proj1/file.c is not mapped, even if
//Acme/proj2/file.c does not exist.