Re: [p4] How to exclude/ignore wildcard in mapping different locations in client spec
jclx <[email protected]>
| Newsgroups | gmane.comp.version-control.perforce |
|---|---|
| Message-ID | <[email protected]> |
Posted on behalf of forum user 'jclx'. Yes that squashing with the same name in your example under A and B is a problem. But in my case the names are all different unique under each path. What is in C1 children will never match what is in C2. But Perforce doesn't know that, I guess. //depot/main/C1/Component1/... //WK/Component1/... //depot/main/C1/Component1a/... //WK/Component1a/... //depot/main/C2/Component2/... //WK/Component2/... //depot/main/C2/Component2a/... //WK/Component2a/... //depot/main/C3/Component3/... //WK/Component3/... Well thanks for confirming that it isn't possible. So we have to explicitly call out each mapping is the only solution for each directory, I have found. But if we add a new child, we have to explicitly map it in the workspace def. So it is a maintenance pain. -- Please click here to see the post in its original format: http://forums.perforce.com/index.php?/topic/5458-how-to-excludeignore-wildcard-in-mapping-different-locations-in-client-spec _______________________________________________ perforce-user mailing list - [email protected] http://maillist.perforce.com/mailman/listinfo/perforce-user