On Wed, Oct 21, 2009 at 01:57:36PM +0200, 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? ___________________________________________________________________
I can see where an explicit flag, say --convert-eol, which changes the end of line according to platform, could be convenient. Maybe allow vars in 'fossil settings' to explicitly configure the eol you want. I would definitely not want default behaviour to change any file. ~Michael _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
