Respectfully, Git still has a long way to go before it achieves parity with Mercurial, or even its state of the art from, say, 2010.<p>Don&#x27;t discount the effect that familiarity with a tool or process can have on your perception of it.  The most succinct explanation of this effect that I know comes from the title of a post on the Light Table blog called, &quot;Pain We Forgot&quot;.<p>Coming from a Mozilla-influenced, pre-GitHub-explosion background, I&#x27;m one of those people always favored Mercurial but used both out of necessity.  Mostly that meant using hg for my own stuff that is most likely never to see the light of day and git for almost everything else.  But I also ended up calling it quits on Mercurial and pulled the trigger on git-for-everything last week.<p>So, having just written (what should be a completely unnecessary) tool to dump out stats about files&#x27; line ending conventions, again, I&#x27;ll say that Git has a long way to go.<p>(And before you ask, yes the problem manifests itself using the latest version of Git, and there&#x27;s nothing exotic or wacky to my workflow, nor am I witnessing the effect of interplay with other tools of dubious quality.  This is an outright case of Git&#x27;s tendency to drop the ball and then gesture in the vague direction of a poorly documented non-fix that cuts orthogonally to the problem it&#x27;s supposed to be solving.)