[p4] typemap issues

Stephen Vance steve at vance.com
Wed Jul 26 11:55:27 PDT 2006

The typemap is only used when files are added. Even then, there's 
nothing preventing the users from overriding that type setting prior to 

To change the type of files that have already been submitted, you will 
need to edit them, changing their type. You will also need to add the 
'-t' flag to your integrations for the type changes to propagate to 
other branches.


Darryl G. Wright wrote:
> Hi there,
> I've added the following to the top of our typemap:
> binary //depot/OurProj/Mainline/data/...
> binary+l //depot/OurProj/Docs/...
> so that nothing under that specific project should be locked when checked 
> out of that particular folder. However, what seems to be happening is that 
> the ones that were already checked out by people (in a locked state) are 
> retaining their binary+l status when they get checked back in again. Is 
> there a way to fix this?
> Note: there is a contradictory statement
> binary+l //....big
> at the bottom of the typemap but I've made the assumption that like the 
> protect table, it would read from the bottom up. Is this a false assumption?
> Thanks,
> Darryl
> ---
> Darryl G. Wright
> Technical Lead
> HB Studios
> http://www.hb-studios.com
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user

More information about the perforce-user mailing list