[p4] Client map too twisted for directory list

[Ivey, William]

> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com]On Behalf Of Stephen Vance
> 
> Wow! It's difficult to even artificially create a client mapping like 
> that! I'd love to see it.

Here's one from one of my (Windows) users that does it:

View:
	//bld/... //KClient/bld/...
	//dev/projA/main/... //KClient/dev/...
	-//dev/projA/main/tools/... //KClient/dev/tools/...
	-//dev/projA/main/TOOLSCD/... //KClient/dev/ToolsCD/...
	//tools/projA/main/tools/... //KClient/dev/tools/...
	//tools/projA/main/TOOLSCD/... //KClient/dev/ToolsCD/...
	//docs/projA/main/... //KClient/docs/...
	//dev/projA/5.1/... //KClient/dev51/...
	-//dev/projA/5.1/tools/... //KClient/dev51/tools/...
	-//dev/projA/5.1/TOOLSCD/... //KClient/dev51/ToolsCD/...
	//tools/projA/5.1/tools/... //KClient/dev51/tools/...
	//tools/projA/5.1/TOOLSCD/... //KClient/dev51/ToolsCD/...
	//docs/projA/5.1/... //KClient/docs51/...
	//qa/... //KClient/qa/...
	//users/... //KClient/users/...
 
His is the only one on our system that triggers the
too twisted error. Oddly enough, several other clients
have similar mappings without a problem, its his
unique combination that seems to do it. (I tried sorting
it out for him once, but when the message went away, his
workspace was no longer mapped exactly as he wanted it
so I let it go and now just ignore the error.)

-Wm