[p4] Client map too twisted for directory list

[Robert Cowham]

> > I think all the exclusionary mappings in this view are unnecessary.
> > For example, the following 3 lines all relate to one another:
> >
> > 1       //dev/projA/main/...         //KClient/dev/...
> > 2      -//dev/projA/main/tools/...   //KClient/dev/tools/...
> > 3       //tools/projA/main/tools/... //KClient/dev/tools/... 
> > 
> > Line 3 and line 1 are in conflict, and Perforce will always use the 
> > latter line to resolve the conflict.  The exlusionary 
> mapping in line 
> > 2 is redundant.
>  
> Perforce views have to be 1:1 in both directions. Without the 
> exclusion mapping, that won't be true. (That is, the path  
> //KClient/dev/tools/... will map to two locations in the
> repository.)

I'm with Shawn on this one. Line 2 is unnecessary. Try taking it out.

In your point the line will map to two locations but the SECOND (LATER) ONE
WILL WIN, so that the first one is ignored. In this instance the first one
is an exclude mapping, but it will still be ignored. So it doesn't hurt but
it isn't necessary.

> However, we probably could use overlay (+) mappings here. 
> That wasn't available when we first started but I think that 
> might work here.

That would do a different thing (depending slightly on actual contents of
files in depot directories).

I talk about overlays on my blog article:

http://www.robertcowham.com/blog/scm/p4_sparse_branching.html

Robert