title: Is it possible for git-merge to ignore line-ending differences?
body: <p>Is it possible for <code>git merge</code> to ignore line-ending differences?</p>
  
  <p>Maybe I'm asking the wrong question ... but:</p>
  
  <p>I tried uisng <code>config.crlf input</code> but things got a bit messy and out of control, specially when I applied it <em>after the fact</em>.</p>
  
  <p>For one thing, applying this config after the fact doesn't seem to affect files that were committed to the repository before applying this option. Another thing is that suddenly all commits now result in lots of annoying warning messages about CRLF being converted to LF.</p>
  
  <p>To be honest, I don't really care what line-ending is used, I personally prefer the Unix style <code>\n</code>, but whatever. All I care about, is for <code>git merge</code> to be a bit smarter and ignore the differences in line-endings.</p>
  
  <p>Sometimes I have two identical files, but git would mark them as being in conflict (and the conflict is the <em>whole</em> file) simply because they use a different line ending character.</p>
  
  <h3>Update:</h3>
  
  <p>I found out that <code>git diff</code> accepts a <code>--ignore-space-at-eol</code> option, would it be possible to let <code>git merge</code> use this option as well?</p>