On Oct 21, 2009, at 7:57 AM, Ramon Ribó wrote: > Hello, > > When developing the same program on Unix and on Windows, cvs > automatically converts the line > end of the files to the appropriates for every platform. In this way, > if we commit a file in windows that > contains "\r\n" as line ends, we can checkout this file on unix and it > will have "\n" line ends. > > As I see, fossil does not change the line endings of the ascii > files. If we try to work as is, I see several > problems, for example, scripts begin with "#!" on unix do not work if > they have "\r\n" as line end" > > What is the opinion of the fossil users & developers on this? What > is the suggested method for developing > the same program in both unix and windows? will fossil be modified in > the future to contain an automatic > translation of line endings?
Fossil was designed with file integrity in mind. The identifier for a file is its SHA1 checksum. If you start changing line-endings, that changes the SHA1 checksum, and the identity of the file. Furthermore, some file formats are broken by changing line endings. Certainly most binary file formats (GIFs, JPEGs) cannot tolerate line- ending changes. But even some text formats (for example the fossil manifest file) require a specific line ending. D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
