Re: [boost] [git] Line endings in bootstrap.bat on Windows

Subject: Re: [boost] [git] Line endings in bootstrap.bat on Windows
From: Dave Abrahams (dave_at_[hidden])
Date: 2013-11-26 22:54:03

Gavin Lambert <gavinl_at_[hidden]> writes:

> On 25/11/2013 14:07, Quoth Dave Abrahams:
>> Björn Pollex <bjoern.pollex_at_[hidden]> writes:
>>
>>> I just cloned the modularized Boost repository from Github [1]. Right after
>>> the clone is done, git status gives me a complete diff on bootstrap.bat (so
>>> probably line endings).
>>>
>>> I do have autocrlf = true in my system configuration, so this shouldn't be
>>> the problem, right?
>>
>> It very well might be the problem.
>
> Provided that the backend repository uses LF line endings exclusively
> (which is the git-recommended style), autocrlf=true is the recommended
> setting on Windows and should not result in a diff being shown if the
> checkout was made with this setting in force. [1][2]
>
> You should only run into trouble if the repository is not LF-only or
> if your checkout contains mixed-EOL files, either from using editors
> that altered EOLs (which will be common on Windows if you don't have
> autocrlf=true) or from changing the autocrlf setting after checking
> out.
>
> If the conversion is not already normalising line endings to LFs,
> perhaps it should do so?  (With some exceptions for test files
> specifically for specific EOL handling, if any.)
>
>
> [1] https://help.github.com/articles/dealing-with-line-endings
> [2] http://git-scm.com/book/ch7-1.html#Formatting-and-Whitespace

The conversion represents the file contents from SVN losslessly.