3 messages in com.perforce.perforce-userQuestion on setting client view| From | Sent On | Attachments |
|---|---|---|
| Shee...@usrl.sony.com | 12 Aug 1998 14:54 | |
| Fred...@mydata.se | 13 Aug 1998 03:46 | |
| Eric...@sybase.com | 13 Aug 1998 12:32 |
| Subject: | Question on setting client view |
|---|---|
| From: | Fred...@mydata.se (Fred...@mydata.se) |
| Date: | 08/13/1998 03:46:47 AM |
| List: | com.perforce.perforce-user |
Sheela Ramakrishnan wrote:
A sample directory structure as: /prac /a /b /c /branch_prac /a
In my client view is it possible to see all files in branch_prac/a/ under prac? Something like: //depot/... //SH_DELL/... -//depot/prac/a/... //SH_DELL/... //depot/branch_prac/a/... //SH_DELL/prac/...
Is this possible? Thanks in advance.
I don't think so.
Here is a quote from 97.3 Users manual chapter 4:
It is possible for multiple mappings in a single view to lead to a situation in which the name does not map the same way in both directions. When a file doesnt map the same way in both directions, the file is ignored.
Joe has constructed a view as follows:
//depot/elm_proj/... //joe/elm/... //depot/nowhere/* //joe/elm/doc/*
The depot file //depot/elm_proj/doc/help would map to //joe/elm/doc/help, but the same file in the client workspace would map back to the depot via the higher-pre-cedence second line to //depot/nowhere/help. Because the file would be written back to a different location in the depot than where it was read from, PERFORCE doesnt map this name at all. In older versions of PERFORCE, this was often used as a trick to exclude particular files from the client workspace. Because PERFORCE now has exclusionary mappings, this type of mapping is no longer useful, and should be avoided.
# From this quote it seems like no files would map to //SH_DELL/proc/...
/Fredric
--- Fredric Fredricson fredric at mydata.se MYDATA automation AB Manager System SW R&D http://www.mydata.se Adolfsbergsvagen 11 phone: +46 8 475 55 21 S-161 70 BROMMA fax: +46 8 475 55 01 SWEDEN