$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [boost] Git Modularization hiccups
From: Jonathan Wakely (jwakely.boost_at_[hidden])
Date: 2013-05-24 07:31:25
On 24 May 2013 12:26, Peter Dimov wrote:
> Jonathan Wakely wrote:
>>
>> Really? How many Windows text editors can't handle non-native line
>> endings these days?
>> (Notepad doesn't count as a text editor, and IMHO it's reasonable to
>> expect Boost contributors to use something other than Notepad - if you
>> can write C++ that works with multiple compilers on multiple platforms
>> then you can use a proper editor.)
>
>
> You have to remember to set the line endings for every new file though.
Only if creating a new file that requires unix line endings, or did I
misunderstand?
I didn't think the suggestion was that all files must have unix line
endings, just that because some require them (e.g. shell scripts with
a shebang) that line endings should be preserved. So if you're
creating a new shell script with a shebang, it should use unix line
endings, but then presumably you'll be creating such scripts on a
unix-like OS anyway and this isn't a problem.