{"thread":{"id":"27887","subject":".gitattributes not forcing EOLs correctly for a CRLF-ending file on *NIX","startedAt":"2011-07-22T13:34:20Z","lastAt":"2011-07-22T13:56:27Z","messageCount":2,"participants":["Adam Monsen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"171841","messageId":"4E297C5C.8030104@gmail.com","threadId":"27887","inReplyTo":null,"subject":".gitattributes not forcing EOLs correctly for a CRLF-ending file on *NIX","fromName":"Adam Monsen","fromEmail":"haircut@gmail.com","sentAt":"2011-07-22T13:34:20Z","receivedAt":"2011-07-22T13:34:20Z","isPatch":false,"sender":{"key":"haircut@gmail.com","avatar":"https://avatars.githubusercontent.com/u/50639?v=4"},"body":"Anyone have ideas why my .gitattributes file isn't working?\n\nRepo:  git://chordii.git.sourceforge.net/gitroot/chordii/chordii\n\nFile \"INSTALL.WINDOWS\" (in the top-level directory of the repo) should\nalways have crlf line endings, but my git 1.7.4.1 client says the file\nis modified after a fresh clone. I'm on Ubuntu GNU/Linux, I have\ncore.autocrlf set to \"input\". The top-level .gitattributes file contains\none line: \"INSTALL.WINDOWS eol=crlf\".\n\nMore likely I'm misusing .gitattributes or the core.autocrlf setting.\n"},{"id":"171842","messageId":"4E29818B.40707@gmail.com","threadId":"27887","inReplyTo":"4E297C5C.8030104@gmail.com","subject":"Re: .gitattributes not forcing EOLs correctly for a CRLF-ending file on *NIX","fromName":"Adam Monsen","fromEmail":"haircut@gmail.com","sentAt":"2011-07-22T13:56:27Z","receivedAt":"2011-07-22T13:56:27Z","isPatch":false,"sender":{"key":"haircut@gmail.com","avatar":"https://avatars.githubusercontent.com/u/50639?v=4"},"body":"I wrote:\n> Anyone have ideas why my .gitattributes file isn't working?\n\ndrizzd on #git helped me out!\n\nI went ahead and committed the file, and git replaced the line endings.\ndrizzd said the repository (the file object, I guess?) contained a file\nwith CRLF line endings, instead of LF line endings. But in my\nchecked-out version, I correctly see a file with CRLF line endings. Yay!\n\nI generally follow the advice at http://help.github.com/line-endings/ in\nterms of the core.autocrlf setting.\n\n"}]}