[p4] Line-ending problems

[Jeff Grills]

Interesting.  I usually use local EOL settings, and then any file that's
particular about its line-ending convention I set as binary instead so that
users/clients can't muck it up.  The downside to my approach is that you
need to pass -t to the diff commands to have them perforce text diffs on
binary files, but that's less common for people to need to do.  I'd rather
require users remember to use a command line option on a read-only command
than forget to set their EOL and mess things by submitting a file with bad
EOL sequences.

I think some MS Visual Studio files (.dsw and .dsp if I recall correctly)
were the most common files for me that needed a specific EOL to function
correctly, and I put in typemap entries to default those extensions to
binary.

j

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Ivey, William
Sent: Monday, February 26, 2007 10:49 AM
To: perforce-user at perforce.com
Subject: Re: [p4] Line-ending problems


[...cut...]

I try to encourage all our users to set their clients to "unix" which
actually does no EOL conversion in practical terms. This works for us
because we have a mix (intentionally) of Windows and unix style files which
must retain their own EOL types. (It does break down when someone reinstalls
Perforce and forgets the default setting is local.)

-Wm