|Title||Perforce documentation unclear about line endings|
|Assigned user||Gareth Rees|
|Description||It is not clear from the documentation what changes Perforce will make to the line endings in the fields in jobs passed to "p4 -G job -i".|
|Analysis||Perforce adds newlines and removes carriage returns from some fields in jobs passed to "p4 -G job -i".|
We can work around any changes that Perforce makes to fields in jobs as long as we know the rules for these changes.
It is critical that we get this right, otherwise the replicator will introduce inconsistencies in line endings between TeamTrack and Perforce, and we will fail to meet requirement 1.
Chris Seiwald documents Perforce's behaviour in [Seiwald 2000-09-28].
|Evidence||[GDR 2000-09-20]; "Line endings in 'p4 -G job -i'?" (e-mail message); Gareth Rees; 2000-09-20 16:44:39 GMT; <URL: |
[Seiwald 2000-09-28a]; "Re: Line endings in 'p4 -G job -i'?" (e-mail message); Chris Seiwald; 2000-09-28 10:02:41 GMT; <URL:
[Seiwald 2000-09-28b] "Re: Line endings in 'p4 -G job -i'?" (e-mail message); Chris Seiwald; 2000-09-28 19:49:45 GMT; <URL:
|Created by||Gareth Rees|
|Created on||2000-09-20 19:15:10|
|Last modified by||Gareth Rees|
|Last modified on||2001-12-10 18:54:17|
|History||2000-09-20 GDR Created.|
2000-09-28 GDR Referenced [Seiwald 2000-09-28a].
2000-09-29 GDR Referenced [Seiwald 2000-09-28b].
2000-10-06 RB Closed by [Seiwald 2000-09-28b], even though this doesn't fix the Perforce documentation as stated. It's as much as we need for P4DTI. They can worry about the rest of the job at their end.
|2593||closed||2000-09-28 20:54:33||Ravenbrook Information System robot||Archiving new mail|
|2576||open||2000-09-28 14:47:50||Gareth Rees||Added Perforce client NTX86/2000.1/17595 to imported materials.|