From: Sergey Lukashev Date: Sun, 27 Jan 2019 11:55:23 GMT Subject: Re: unclear docs Message-ID: <13169311548590123@iva1-16f33c6a446b.qloud-c.yandex.net> In-Reply-To: <57362151548583138@iva8-37fc2ad204cd.qloud-c.yandex.net> A follow up on my previous mail. Well, I have two problems: 1) The endings I get with core.autocrlf=false depend on whether I have * text=auto (a file was commited with LFs). At least in git 2.20.1 2) If the quote holds true then autocrlf=false is actually "true" (for output conversion) on Windows by default because default core.eol is 'native', which is CRLF. I believe autocrlf=false is supposed to mean "no any conversion, input or output, read or write the repo as is". 27.01.2019, 13:05, "Sergey Lukashev" : > Hello! > > Could somebody please explain what 'core.autocrlf overrides core.eol' means given that we have the following statement in core.eol docs: > "Sets the line ending type to use in the working directory for files that have the text property set when core.autocrlf is false". > > I would like to know which line endings I'm supposed to get in the working tree if I have core.autocrlf=false and '* text=auto' in .gitattributes on windows. I get CRLFs which is consistent with the last quote but I don't understand what 'core.autocrlf overrides core.eol' means in this case. > > Links: > https://git-scm.com/docs/git-config#git-config-coreeol > https://git-scm.com/docs/gitattributes#_checking_out_and_checking_in