[p4] change filetypes for whole subtree?

Robert Cowham robert at vaccaperna.co.uk
Fri May 11 07:43:45 PDT 2007


For a similar script:

http://www.robertcowham.com/blog/scm/p4_handling_keywords.html

Robert 

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Qazwart
> Sent: 11 May 2007 01:35
> To: William Deegan
> Cc: Perforce Users
> Subject: Re: [p4] change filetypes for whole subtree?
> 
> That's been a big problem with RCS keyword expansion: You 
> can't easily find true diffs. Even in CVS, I would have to 
> fix merges where the whole "conflict" was the RCS string change.
> 
> I wrote a quickie Perl script to copy all the files in the 
> directory into another directory and "unexpand" the RCS Keywords.
> 
> I don't have the script, but it wasn't too difficult. I used 
> the "File::Find" module,  and used the substitution pattern 
> s/$(Author| 
> Date|Id|State):\$/\$$1:$/g (or something like that). The only real
> troublemaker is the "$Log$" keyword. If you have that, you're 
> basically out of luck.
> 
> On May 10, 2007, at 5:55 PM, William Deegan wrote:
> 
> > Greetings,
> >
> > I used cvs2p4 and it created all the files as type ktext, which I'd 
> > like to undo.
> > Can I change all the files back and get the original $Id $ values 
> > which were imported?
> > I want to verify the cvs checked out files match the 
> perforce checked 
> > out imported files, and of course since the $Id $ is 
> getting expanded 
> > all files are showing differences..
> >
> > Thanks,
> > Bill
> > _______________________________________________
> > perforce-user mailing list  -  perforce-user at perforce.com 
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> 
> David Weintraub
> david at weintraub.name
> qazwart at gmail.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