On Sun, 25 Nov, Jan Nijtmans wrote: > The crnl warning is meant to tell people: be carefull, what you > are doing works fine on Windows, but not on UNIX. The > unicode warning works the same: this file will probably > work fine on Windows, but in UNIX project, most likely not. > I would be fine with a combined "crnl-glob" and > "unicode-glob" (windows-glob, maybe?), saying: what > you are doing is windows-specific.
It's just about the format of data one puts into fossil. If I commit a PowerPoint file, I wouldn't expect a warning "this file will not work on UNIX". Neither do I expect such a warning when I commit UTF-16 or CR/NL data. It's all about the file format and the tools used to operate on them. If you have the proper tools installed, you can perfectly handle UTF-16, CR/NL and even PowerPoint files on UNIX. > Partly, "-f" already functions like that, although -f does more: It > permits no-op commits as well. I was not able to commit using the -f flag in order to override the CR/NL and the Unicode warning. Not sure about the binary warning, I haven't tested that separately. Greetings, Stefan -- Stefan Bellon _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
