Good to know! This came about from supporting data files supplied by various users and I still receive the occasional [CR] only data file?
On Thu, Apr 7, 2011 at 12:33 PM, Konstantin Khomoutov <flatw...@users.sourceforge.net> wrote: > On Thu, 7 Apr 2011 12:04:44 -0400 > sky5w...@gmail.com wrote: > >> I would be immensely confused if my SCM was modifying the contents of >> my source code and/or support documents. >> Given that MacOS has yet another EOL = [CR], it is better for your own >> code to manage distribution effects. > I think it's no longer true: CR was used on prehistoric Macs (those > from eighties); contemporary Macs are quite POSIX'y and have LF as a > conventional line-ending marker. > > As to imaginable hassles of auto-conversions, I think this is an > exaggregation: Subversion and Git do this for ages and there's no > apparent complaints about how they do this. > In case you're interested, here are explanations on how they do this: > > http://svnbook.red-bean.com/en/1.5/svn.advanced.props.file-portability.html#svn.advanced.props.special.eol-style > > http://www.kernel.org/pub/software/scm/git/docs/git-config.html > (see core.eol, core.safecrlf, core.autocrlf; Git for Windows has > core.autocrlf set to true by default). > _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
