title: Should the .gitattributes file be in the commit?
body: <p>We're working on a project with a few people having a Mac, and I am running on Windows. We get some problems with the linebreaks.</p>
  
  <p>I read on GitHub that I could add this:</p>
  
  <pre><code># Set default behaviour, in case users don't have core.autocrlf set.
  * text=auto
  
  # Explicitly declare text files we want to always be normalized and converted
  # to native line endings on checkout.
  *.c text
  *.h text
  
  # Declare files that will always have CRLF line endings on checkout.
  *.sln text eol=crlf
  
  # Denote all files that are truly binary and should not be modified.
  *.png binary
  *.jpg binary
  </code></pre>
  
  <p>Into .gitattributes</p>
  
  <p>But should I commit that file to GitHub so the other people with Macs get the same settings?</p>
  
  <p>If it matters, we're coding websites. (PHP, JavaScript files, and stuff).</p>
  
  <p>For the record, I'm the only one with Windows... So yeah, what can I do?</p>