git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: unclear docs

From
SLSergey Lukashev <lukashev.s@ya.ru>
Date
Jan 27, 2019, 11:55 UTC
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" <lukashev.s@ya.ru>:
Show 10 quoted lines
> 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
Previous: Sergey LukashevNext: Jeff King
Message 2 of 16 in “unclear docs”
  1. Sergey LukashevJan 27, 2019
  2. Sergey LukashevJan 27, 2019
  3. Jeff KingJan 28, 2019
  4. Sergey LukashevJan 28, 2019
  5. Jeff KingJan 28, 2019
  6. Torsten BögershausenJan 29, 2019
  7. Sergey LukashevJan 29, 2019
  8. 0/2 eol/autocrlf doc clarificationsJeff King, Jan 29, 2019
  9. 1/2 doc/gitattributes: clarify "autocrlf overrides eol"Jeff King, Jan 29, 2019
  10. 2/2 docs/config: clarify "text property" in core.eolJeff King, Jan 29, 2019
  11. Torsten BögershausenJan 28, 2019
  12. Jeff KingJan 28, 2019
  13. Junio C HamanoJan 28, 2019
  14. Jeff KingJan 28, 2019
  15. Sergey LukashevJan 28, 2019
  16. Jeff KingJan 28, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.