Hello, I want to throw in my 2 cents, too.
I don't see why fossil shouldn't provide any facility to run files through a filter or preprocessor before checkin, after check out and maybe there are other actions when running a file through a filter is useful or necessary. When a developer uses this filter for converting line endings, let her do so. Maybe someone wants to indent source files before checkin. There are many cases where it makes sense to the developer. Ruediger Am Mittwoch 21 Oktober 2009 schrieb Ramon Ribó: > 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-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
