[Top][All Lists]

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

Re: [gnugo-devel] Lack of files in CVS \gnugo\patterns\

From: Paul Pogonyshev
Subject: Re: [gnugo-devel] Lack of files in CVS \gnugo\patterns\
Date: Thu, 5 Dec 2002 00:43:32 +0200

> As far as I know, every file is treated the same regarding
> CR LF endings. If it is checked in with CR LF, when checked
> out it ends the same way. If one line ends with LF, it is
> the same when it is checked out.  If they are getting
> checked out as CR CR LF I think the cvs client is at fault.

Dan, it's not a cvs client fault, it's cvs client _documented_
behaviour. you cannot check without having a cvs client on a
system which has line endings other than LF.

File:,  Node: Binary howto,  Prev: Binary why,  Up: Binary files

How to store binary files

   There are two issues with using CVS to store binary files.  The
first is that CVS by default converts line endings between the
canonical form in which they are stored in the repository (linefeed
only), and the form appropriate to the operating system in use on the
client (for example, carriage return followed by line feed for Windows

when on M$ system, cvs checks out files which have LF line ends in
the repository with CR LF line ends. it assumes that files having
CR LF in the repository have LF for line end and CR as a plain
character. so, it converts LF to CR LF and writes CR CR LF to a
local file copy.


reply via email to

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