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

Explanation of `eol` attribute doesn't seem correct for Windows machines

From
HMHans Meiser <brille1@hotmail.com>
Date
Nov 6, 2023, 15:11 UTC
Message-ID
<AS4P195MB15272FE283D0CF606A8B074EE2AAA@AS4P195MB1527.EURP195.PROD.OUTLOOK.COM>
https://git-scm.com/docs/gitattributes#_eol
claims that:

--- Set to string value "crlf"

    This setting converts the file’s line endings in the working directory to CRLF when the file is checked out.
Set to string value "lf"
    This setting uses the same line endings in the working directory as in the index when the file is checked out.
---
I don't think this explanation is sufficient for files stored on Windows machines. A file might be stored with CRLF in the index. What happens then? And what happens when a file is added to the index with `core.autocrlf=input` on Windows machines?
Next: Torsten Bögershausen
Message 1 of 4 in “Explanation of `eol` attribute doesn't seem correct for Windows machines”
  1. Hans MeiserNov 6, 2023
  2. Torsten BögershausenNov 6, 2023
  3. Hans MeiserNov 7, 2023
  4. Torsten BögershausenNov 7, 2023

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.