[p4] Doubt with exclusion principle...

steve at vance.com steve at vance.com
Fri Nov 24 10:59:21 PST 2006


The right hand side has to parallel the left hand side.  For example, it
should be

-//depot/rel1/... //sushree_ws/rel1/...

Steve

Original Message:
-----------------
From: Sushree Tripathy sushreetripathy at yahoo.com
Date: 	Fri, 24 Nov 2006 00:43:51 -0800 (PST)
To: perforce-user at perforce.com
Subject: [p4] Doubt with exclusion principle...


Hi All,

I have tried to explain a situation below...
  
I have a client sushree_ws
view : //depot/... sushree_ws/...
       -//depot/rel1/... //sushree_ws/...
       -//depot/main/... //sushree_ws/...

I have a branch spec rel2
view : //depot/... //depot/rel2/...
       -//depot/main/... //depot/rel2/...
       -//depot/rel1/... //depot/rel2/...

I have files at depot level.
//depot/a.c
//depot/b.c
//depot/c.c

Using the above client spec if i try and sync it says
File(s) not in client view.

Then I changed the client spec to
view : //depot/... sushree_ws/...
I got all the files from main and rel1 to the
workspace

Now if I follow a branch using the above branch spec I
get all the files from main and rel1 branched to
//depot/rel2/...

Queries:
Why is Perforce including main and rel1 evenif we have
excluded it?

How/Where the exclusion principle(- sign) works?

I could branch the files at depot level to rel2 using
the file specification but I want to know in depth
obout the use of the exclusion principle, I mean the
underlying concept...

Please share your expertise...

-Sushree.






 
____________________________________________________________________________
________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .





More information about the perforce-user mailing list