Re: WINCVS and MSVC problem

[Kaz Kylheku]

In article <address@hidden>, Stephan Feder wrote:
>Larry,
>
>I know how the cvs client handles line endings but nonetheless it is a
>problem for quite a few users. What about a flag for the client that
>prevents it from doing _any_ line ending conversions (as I understand it
>the server transfers the files as they are)?

You misunderstand. The problem is that some idiots took DOS text files
sitting on a Linux client, and imported or added them to CVS.

This is not a CVS problem at all.  It's a problem between the keyboard
and chair.

If you have a bunch of text files, and they are correctly represented
text files for the operating system you are using, you can put them
into CVS. Someone can check them out on a different operating system,
and CVS will convert them to proper text files for that operating system.

When you add or import files, you can specify that they are to be treated
as binary. Binary files don't undergo line ending conversions.

Whether a file is text or binary is an essential, inherent property
of that file. It's not something you want to be turning on and off at
transport time.

One solution in your case is to check out the erroneous files, fix their
broken line endings, and commit the changes. Changing the client behavior
on checkout is the wrong solution to the wrong problem.