[p4] Integrating file-type changes automatically?

Julian Foad Julian.Foad at sepura.com
Fri Nov 16 01:50:18 PST 2007


So have any of you investigated creating your own external solution? If
you have, and found it impossible or difficult or not worthwhile for
some reason, I'm keen to hear.

I assume you've all just been living with the awkward manual ways like
we have.

- Julian


> -----Original Message-----
> From: steve at vance.com [mailto:steve at vance.com] 
> 
> I made a request shortly after they added the '-t' option to 
> integrate (in 2000.2) ...
> 
> -----Original Message-----
> From: Brad Holt
> 
> Sorry, I don't want to take the thread off of Julian's 
> request, but ...
> 
> Anyway, back to Julian's question which I would also be keen 
> to hear an answer to...
> 
> -----Original Message-----
> From: Julian Foad
> 
> Anyone written a script to integrate file-type changes 
> (especially adding or removing the "k" and "x" modifiers) 
> during a normal integration?
> 
> For those who aren't familiar with the problem, it's that "integ"
> ignores file type changes by default, and the only built-in 
> alternative is the "integ -t" option which blindly copies the 
> file-type information from the source file to the destination 
> file regardless of whether it's been changed on either (or both).
> 
> Using this option manually is too prone to user error. 
> Ideally, we wish these changes would be integrated just like 
> file-content changes are, including conflict resolution. As a 
> good-enough solution we are looking for something (a trigger 
> script, probably) that at least handles the type having been 
> changed on either the source or the destination but not both, 
> and propagates it or not accordingly.
> 
> If no-one has written such a thing, is that because it's 
> difficult or there's a better way?
> 
> Thanks.
> --
> Julian Foad
> Senior Software Engineer
> 
> Sepura plc
> 100 Longwater Avenue
> Green Park
> Reading
> Berkshire
> RG2 6GP
> 
> T: +44 (0)1223 874662
> F: +44 (0)118 9450116
> www.sepura.com
> 
> ______________________________________________________________
> 
> The information in this email is confidential.  It is 
> intended solely for the addressee.  Access to this email by 
> anyone else is unauthorised.
> If you are not the intended recipient, any disclosure, 
> copying, or distribution is prohibited and may be unlawful.  
> If you have received this email in error please delete it 
> immediately and contact commercial at sepura.com.
> 
> Sepura plc. Registered Office: Radio House, St Andrew's Road,
Cambridge,
> CB4 1GR, England. Registered in England and Wales. Registration Number
> 4353801
> ______________________________________________________________

_______________________________________________________________________

The information in this email is confidential.  It is intended
solely for the addressee.  Access to this email by anyone else
is unauthorised.  If you are not the intended recipient, any
disclosure, copying, or distribution is prohibited and may be
unlawful.  If you have received this email in error please delete
it immediately and contact commercial at sepura.com.

Sepura plc. Registered Office: Radio House, St Andrew’s Road, Cambridge, CB4 1GR, England. Registered in England and Wales. Registration Number 4353801

_______________________________________________________________________

This e-mail has been scanned for all viruses by Star Internet.
The service is powered by MessageLabs.



More information about the perforce-user mailing list