The "crlf-glob" setting allows files to have CR, CR+LF or mixed line endings. The "--no-warnings" option for "fossil commit" works analogously (and also affects warnings about binary files).
As a (mostly) Windows user, I would appreciate a way to silence warnings for all files with *consistent* line endings (CR, CR+LF, and LF), but still display a warning for files with *mixed* line endings, or *binary* contents. Decent text editors ensure consistent line endings, but files auto-generated from various sources, or modified using command-line tools, can still have mixed line endings. This sounds like a simple change, but from looking at the Fossil source code, it seems less trivial, as the decisions about line ending warnings are all coalesced to single "crlfOk" variables. Maybe a new "crlf-consistency" setting (to alphabetically sort near "crlf-glob", but work independently) is the best way to implement this? A new command line option for "fossil commit" may also be required, so as not to change workflow? I hope that this feature request is of enough general interest, so that you may consider adding it. Thank you very much! --Florian _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
