I&#x27;ve tried to write and rewrite this comment, but it oozes disdain every time.  So here&#x27;s my best:<p>I expect that if a file uses CRLF everywhere, `git merge` will not leave it in a state with mixed line endings after inserting conflict resolution markers that end in LF instead of CRLF.<p>This shouldn&#x27;t require a configuration option, but if it does, fine.  However, Git doesn&#x27;t even seem to have this.<p>What it does have are &#x27;autocrlf&#x27; and &#x27;eol&#x27; and &#x27;text&#x27; options&#x2F;attributes.  For anyone who mentions those, I&#x27;m going to ask that you be familiar with not just what those actually control, but also how they&#x27;re documented in the git man pages and in the book from git-scm.org—the entire premise was a discussion about Git&#x27;s user-facing parts.  By either source, those options control line normalization (i.e., implicit automatic conversion), which is not what I&#x27;m talking about.  And the documentation for those is sick enough that even if they <i>were</i> the things to look to in order to configure this, then the idea that Git&#x27;s UI is on par with Mercurial nowadays would still be wrong.<p>EDIT: To clarify, the desired approach for this is, &quot;Use whatever line endings the file is already using&quot;.  Git&#x27;s approach to this is, &quot;Standardize on either LF or CRLF, and at your discretion enable what amounts to some glorified git hooks to ensure that policy is followed, through the use of some obtusely documented configuration options.  Make sure to work around any problems with <i>that</i> (e.g., when it&#x27;s corrupting files that should have never been normalized) by applying another liberal layer.&quot;