{"thread":{"id":"31620","subject":"What are the ways CRLF files can make it into the repository?","startedAt":"2012-09-21T19:02:11Z","lastAt":"2012-09-22T12:08:21Z","messageCount":2,"participants":["Joshua Jensen","Konstantin Khomoutov"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"199685","messageId":"505CB9B3.5010307@workspacewhiz.com","threadId":"31620","inReplyTo":null,"subject":"What are the ways CRLF files can make it into the repository?","fromName":"Joshua Jensen","fromEmail":"jjensen@workspacewhiz.com","sentAt":"2012-09-21T19:02:11Z","receivedAt":"2012-09-21T19:02:11Z","isPatch":false,"sender":{"key":"jjensen@workspacewhiz.com","avatar":"https://avatars.githubusercontent.com/u/111687?v=4"},"body":"Hi.\n\nWe've been running with core.autocrlf = input (some people with \ncore.autocrlf = true).  However, there are some text files in the \nrepository that are CRLF, and I am at a loss to explain how they go here.\n\nWe understand that if core.autocrlf=false, this could happen.  While I \nadmit there is a remote possibility this did occur, I'm not convinced \nour people were smart enough with Git 1.5 years ago to make this \nconfiguration change.\n\nThere are no .gitattributes settings for these source code files.\n\nAre there other ways CRLF files could sneak into the repository?\n\nThanks.\n\nJosh\n"},{"id":"199737","messageId":"20120922120821.GI32381@localhost.localdomain","threadId":"31620","inReplyTo":"505CB9B3.5010307@workspacewhiz.com","subject":"Re: What are the ways CRLF files can make it into the repository?","fromName":"Konstantin Khomoutov","fromEmail":"flatworm@users.sourceforge.net","sentAt":"2012-09-22T12:08:21Z","receivedAt":"2012-09-22T12:08:21Z","isPatch":false,"sender":{"key":"flatworm@users.sourceforge.net","avatar":null},"body":"On Fri, Sep 21, 2012 at 01:02:11PM -0600, Joshua Jensen wrote:\n\n> We've been running with core.autocrlf = input (some people with\n> core.autocrlf = true).  However, there are some text files in the\n> repository that are CRLF, and I am at a loss to explain how they go\n> here.\n> \n> We understand that if core.autocrlf=false, this could happen.  While\n> I admit there is a remote possibility this did occur, I'm not\n> convinced our people were smart enough with Git 1.5 years ago to\n> make this configuration change.\n> \n> There are no .gitattributes settings for these source code files.\n> \n> Are there other ways CRLF files could sneak into the repository?\nIs there any chance Git considered them binary for some reason and hence\ndid not apply its EOL-conversion logic at all?\n"}]}