threads / discuss / 27887

.gitattributes not forcing EOLs correctly for a CRLF-ending file on *NIX

Subject: .gitattributes not forcing EOLs correctly for a CRLF-ending file on *NIX

## tl;dr

2 messages between Jul 22, 2011 and Jul 22, 2011.

replies: 1people: 1as markdown or json

Adam Monsen· Jul 22, 2011, 13:34 UTC · lore

Anyone have ideas why my .gitattributes file isn't working?

Repo:  git://chordii.git.sourceforge.net/gitroot/chordii/chordii

File "INSTALL.WINDOWS" (in the top-level directory of the repo) should always have crlf line endings, but my git 1.7.4.1 client says the file is modified after a fresh clone. I'm on Ubuntu GNU/Linux, I have core.autocrlf set to "input". The top-level .gitattributes file contains one line: "INSTALL.WINDOWS eol=crlf".

More likely I'm misusing .gitattributes or the core.autocrlf setting.

Adam Monsen· Jul 22, 2011, 13:56 UTC · re: Adam Monsen · lore

Re: .gitattributes not forcing EOLs correctly for a CRLF-ending file on *NIX

I wrote:

> Anyone have ideas why my .gitattributes file isn't working?

drizzd on #git helped me out!

I went ahead and committed the file, and git replaced the line endings. drizzd said the repository (the file object, I guess?) contained a file with CRLF line endings, instead of LF line endings. But in my checked-out version, I correctly see a file with CRLF line endings. Yay!

I generally follow the advice at http://help.github.com/line-endings/ in terms of the core.autocrlf setting.