[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: dos2unix file endings

From: Rez P
Subject: RE: dos2unix file endings
Date: Fri, 30 Oct 2009 15:14:03 -0700

Thanks for your thorough reply Spiro.  I suspected that they were ending up 
with the correct file endings on each environment respectively and that the 
wincvs client was converting them.  So it looks like once I check them out, I 
have to run dos2unix on them and tar them up and ship them back to our 
application servers.  thanks  again.
> Date: Fri, 30 Oct 2009 22:18:57 +0100
> From: address@hidden
> To: address@hidden
> Subject: Re: dos2unix file endings
> Hello Rez,
> * On Fri, Oct 30, 2009 at 01:03:36PM -0700 Rez P wrote:
> > Although they get created on Window client machines, how can I ensure
> > once they're checked in, they get checked in with Windows file format
> > endings stripped off?
> This is standard behaviour of CVS as long as you have not configured
> anything else. Every text file is checked in with Unix line endings (LF)
> only. In fact, you must explicitly mark a file as binary to check in the
> Windows line endings.
> Having said that, I do not know what exact behaviour WinCVS has here. It
> might mess with that somehow. I never used WinCVS but for some small
> tests, thus, I cannot comment. WinCVS uses CVSNT internally, which is a
> different thing than CVS. 
> So, why do you see Windows line endings when you check out? That's
> because the CVS client tries to adapt to the line endings that are
> present on the system it works. Thus, the CVS changes LF -> CR/LF when
> you are using a native Windows client.
> (Note: IIRC, the Cygwin CVS client will check out with Unix line endings
> if Cygwin is set to Unix line endings. You might want to use that)
> To make a long story short: Regardless of the line endings you see on
> your Windows system, as long as you do not check in the files as binary
> (-kb) explicitly, the files are stored the Unix line endings on the
> server. Thus, checking them out on a Linux machine will give them the
> correct line endings. (I assume WinCVS + CVSNT behave the same here, or
> you have a problem with them. They have a different mailing list,
> though.)
> Thus, I would not care about the line endings on Windows. If you really,
> really need it different, then 
> 1. use CVS from Cygwin, or
> 2. mark all files as binary and make sure you check them in after
> dos2unix only
> HTH,
> Spiro.
> -- 
> Spiro R. Trikaliotis
Windows 7: Simplify your PC. Learn more.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]