[MinGW-dvlpr] CVS

[Wu Y. <ad...@ne...>]

I see ....

I think it's better that you stick to a Unix-like enviroment like Cygwin, or
choose a line-ending-sensitive CVS client like the one distributed with
WinCVS.

I myself am using WinCVS with a Linux CVS server and have found no problems.
The line endings are converted transparently.

I wondered if the problem could be produced by the difference between SSH
and PServer. I am using PServer. When I use SSH with CVS, I use Cygwin so no
line-ending problems are expected. But my test confirmed that using my CVS
with Cygwin SSH caused no problems: local files have CRLF and server files
have only LF.

My last wonder is that somebody mixed the use of two versions of CVS: check
out with Windows CVS, but commit with Cygwin CVS? Or using Cygwin CVS but
mistakenly using a editor that converts LF to CRLF?

Bottom line: use Unix-style CVS but never use a Windows editor that does not
support Unix line ending (edit.com, MSVC editor, etc.).

Best regards,

Wu Yongwei

--- Original Message from Luke Dunstan ---

The Windows CVS client that I am talking about does not do any explicit
translation or canonicalization in the sense that you mean: it simply opens
files in text mode whenever reading or writing a non-binary file. This means
that when you check in a file that has DOS line endings on a Unix system (or
Cygwin/MSYS), the \r's will be stored on the server, and when checking out
the file on Windows, the file will be opened in text mode so "\r\n" becomes
"\r\r\n". Here I am talking about the "official" CVS client from
cvshome.org, and the same happens with the client that comes with
TortoiseCVS (I don't know about WinCVS).

Luke