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

what the text=auto docs should be

From
Cameron Taggart <cameron.taggart@gmail.com>
Date
Feb 16, 2014, 05:36 UTC
Message-ID
<CAABik=swf_FLpnKOxehbfxu+pEx2wN7Tnw+=VQRAp2_DMR0+nQ@mail.gmail.com>

It would be better if the text=auto section of the gitattributes Manual Page had this:

This ensures that all files that git considers to be the text will have normalized (LF) line endings in the repository. If core.autocrlf=true, core.eol will be used to normalize the files in your working directory. core.eol defaults to native line endings for your platform.

I researched and put my thoughts down in a blog post: http://blog.ctaggart.com/2014/02/time-to-kill-carriage-return.html

cheers, Cameron

Message 1 of 1 in “what the text=auto docs should be”
  1. Cameron TaggartFeb 16, 2014

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.