Thread (2 messages) flat view 2 messages, 2 authors, 2016-06-15

Issues with line-endings and autocrlf setting after SVN to Git transition

From: Bradley Wagner <hidden>
Date: 2016-06-15 22:49:04

So I'm running into the infamous issue with line-endings after
migrating an SVN repo to Git.

I'm on OS X and I currently have auto.crlf set to "input" as
recommended on this GitHub page:
http://help.github.com/dealing-with-lineendings/. I'm doing a fresh
clone of our repo and it's showing many files as having changed.

I've gotten conflicting answers to my question on Stack Overflow:
http://stackoverflow.com/questions/3161797/will-the-fix-to-correct-line-endings-in-git-repositories-make-future-diffs-usel.
Should I fix this with a commit or turn off autocrlf? I intend to use
this repo in both OS X and Windows environments. The problem with
fixing it with a commit is that the commit will change every single
line of these affected files. As I understand it from SVN, this means
that any diffs that span that commit will basically show the entire
files as being changed which is definitely frustrating.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help