From: Sergey Lukashev <lukashev.s@ya.ru>
Date: Mon, 28 Jan 2019 20:16:54 GMT
Subject: Re: unclear docs
Message-ID: <1811741548706614@myt1-06117f29c1ea.qloud-c.yandex.net>
In-Reply-To: <20190128183253.GB13165@sigill.intra.peff.net>

autocrlf can be "input" as well.

28.01.2019, 21:32, "Jeff King" <peff@peff.net>:
> On Mon, Jan 28, 2019 at 10:30:31AM -0800, Junio C Hamano wrote:
>
>>  Jeff King <peff@peff.net> writes:
>>
>>  > I think it means:
>>  >
>>  > - if core.autocrlf is false (the default), then the text attribute and
>>  > core.eol are used
>>  >
>>  > - if core.autocrlf is true, then that overrides the whole
>>  > attribute/eol system
>>
>>  I think that matches my understanding.
>>
>>  > Subject: [PATCH] doc/gitattributes: clarify "autocrlf overrides eol"
>>  >
>>  > We only override core.eol with core.autocrlf when the latter is set to
>>  > "true" (otherwise, core.eol would never do anything!). Let's make this
>>
>>  I fail to understand what "otherwise..." wants to say. When
>>  core.autocrlf is not "true", core.eol would not do anything?
>
> I meant that if core.autocrlf overrides core.eol also when it is not set
> to true, then there would be no way to use core.eol, because the former
> must be either true or false.
>