Re: 'eol' documentation confusion

From: Torsten Bögershausen <tboegi@web.de>
Date: Jun 22, 2015, 06:26 UTC
Message-ID: <5587AAB2.80305@web.de>
In-Reply-To: <CAHd499Do_bpdOkL2TqdO+8L=pR53117pKR0GSwdgvFDwq_S4=w@mail.gmail.com>

On 06/21/2015 04:16 PM, Robert Dailey wrote:

Show 14 quoted lines

> On Sun, Jun 21, 2015 at 9:04 AM, Robert Dailey <rcdailey.lists@gmail.com> wrote:
>> Upon inspection of the gitattributes documentation page here:
>> https://git-scm.com/docs/gitattributes
>>
>> When comparing the documentation for 'text' with 'eol', I see the
>> following missing explanations for 'eol':
>>
>> * eol
>> * -eol
>>
>> Maybe the fact that these are missing means they are not valid to use.
>> There is also the issue that `text` usually controls EOL anyway. Is
>> there ever any reason to set eol in a way differently than explained
>> in the documentation (that is, `eol=lf` or `eol=crlf`)?

No. eol=lf or eol=crlf are the only useful settings. Everything else is ignored because it does not make sense.

See convert.c: static enum eol git_path_check_eol()