[p4] typemap issues
dfaison at photon.com
Wed Jul 26 14:45:07 PDT 2006
>> So is it a case where now that I've changed the setting in the
>> type-map they'll have to delete and re-add all those binary files to
>> ensure they're shareable?
The situation is not nearly that bad... just dump a list into a file of
all the binary files that need to have the "+l" modifier removed (let's
call it "binfiles.lst") and issue the following command:
"p4 -x binfiles.lst edit -t binary"
Submit the resulting changelist and you are done!
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Darryl G.
Sent: Wednesday, July 26, 2006 4:20 PM
To: Stephen Vance
Cc: 'Jim O'Brien'; perforce-user at perforce.com
Subject: Re: [p4] typemap issues
The real issue is that we want to be able to allow 2 users to edit the
binary file at the same time. Currently, it seems that since the
flag was added globally by another project that shares our depot (thus
accidentally making all our binary files locked as well) our people can
longer share most of the binary files that used to be shared. So is it a
case where now that I've changed the setting in the type-map they'll
to delete and re-add all those binary files to ensure they're shareable?
Stephen Vance wrote:
> The typemap is only used when files are added. Even then, there's
> nothing preventing the users from overriding that type setting prior
> 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
>> 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
>> Darryl G. Wright
>> Technical Lead
>> HB Studios
>> perforce-user mailing list - perforce-user at perforce.com
Darryl G. Wright
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user