7 messages in com.perforce.perforce-userCR/LF terminations in perforce
FromSent OnAttachments
Keesee17 Mar 1998 11:13 
Pete...@auspex.com17 Mar 1998 11:21 
Tony...@illustra.com17 Mar 1998 11:26 
Mark...@discerning.com17 Mar 1998 21:15 
Pete...@auspex.com18 Mar 1998 08:25 
Mark...@discerning.com18 Mar 1998 08:57 
Marc...@mpath.com18 Mar 1998 09:39 
Subject:CR/LF terminations in perforce
From:Mark...@discerning.com (Mark@discerning.com)
Date:03/18/1998 08:57:28 AM
List:com.perforce.perforce-user

Anyway, now that I've ranted on what I want and how I think it should work, what can I actually get, and how should I get it?

I think today that means making them binary.

Which means that we lose delta-based storage, which is a royal PITA.

Also, there is no way to set project defaults (is there?). The heuristic p4 uses to guess the appropriate type is compiled-in, so this means that all users will have to remember to do a -t. Some won't, which will induce later wailing and gnashing of teeth. And there is no way to do "pre-triggers" to enforce it either (is there?), just post-triggers ("daemons").

Part of the problem here is a confounding by perforce of different kinds of "type". There is a single type setting to determine both view settings (file permissions, etc.) and storage encoding.

- -mda