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

Re: What are the ways CRLF files can make it into the repository?

From
KKKonstantin Khomoutov <flatworm@users.sourceforge.net>
Date
Sep 22, 2012, 12:08 UTC
Message-ID
<20120922120821.GI32381@localhost.localdomain>
In-Reply-To
<505CB9B3.5010307@workspacewhiz.com>
On Fri, Sep 21, 2012 at 01:02:11PM -0600, Joshua Jensen wrote:
Show 13 quoted lines
> We've been running with core.autocrlf = input (some people with
> core.autocrlf = true).  However, there are some text files in the
> repository that are CRLF, and I am at a loss to explain how they go
> here.
> 
> We understand that if core.autocrlf=false, this could happen.  While
> I admit there is a remote possibility this did occur, I'm not
> convinced our people were smart enough with Git 1.5 years ago to
> make this configuration change.
> 
> There are no .gitattributes settings for these source code files.
> 
> Are there other ways CRLF files could sneak into the repository?

Is there any chance Git considered them binary for some reason and hence did not apply its EOL-conversion logic at all?

Previous: Joshua Jensen
Message 2 of 2 in “What are the ways CRLF files can make it into the repository?”
  1. Joshua JensenSep 21, 2012
  2. Konstantin KhomoutovSep 22, 2012

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.