git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Bradley Wagner <bradley.wagner@hannonhill.com>
Date
Jul 2, 2010, 19:59 UTC
Message-ID
<AANLkTilsvEbwHhIkvpaZQ4542tH2i6qF4EZR1IjErp46@mail.gmail.com>

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.

Next: Eyvind Bernhardsen
Message 1 of 2 in “Issues with line-endings and autocrlf setting after SVN to Git transition”
  1. Bradley WagnerJul 2, 2010
  2. Eyvind BernhardsenJul 3, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.