AFAIK, cvs only converts line-endings when it detects the client is a different
platform, however, if you check in or import DOS files (with CR/LFs) from a Unix
client, no conversion will be done. If your developers are using a decent editor on
the windoze side, then a lack of CRs should not be a problem (the editor should detect
the file type, and allow conversion if desired). OTOH, if you try and process/compile
source files with CRs on the unix/linux side, then there may be problems caused by the
extraneous CRs. I would keep the files in LF format if possible, and only convert to
the DOS format when required. Then they'll need to commit those files from a winCVS
client to convert them back again (i.e., only keep LF-terminated files in the
repository).
Just my $.02
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 06, 2000 8:09 AM
> To: [EMAIL PROTECTED]
> Subject: Unix to Dos filtering
>
> Client developers on my site, checkout code on unix
> machines. They then use
> the checked out code on Windows using Samba. How do i make
> sure that when they
> check the files out on unix, it automatically put the Ctrl Ms
> on these DOS-type
> files?
> If a file is checked in with Ctrl Ms on unix, are the
> Ctrl Ms retained on
> another checkout or during commit? (All cvs commands are run on unix).
