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

Re: git blame breaking on repository with CRLF files

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 10, 2015, 18:48 UTC
Message-ID
<xmqq1tfbugho.fsf@gitster.dls.corp.google.com>
In-Reply-To
<55C7B5EE.7060908@web.de>
Torsten Bögershausen <tboegi@web.de> writes:
> Actually I could reproduce the following:
> CRLF in repo, CRLF in working tree, core.autocrlf= true.

What should happen in such a case? Wouldn't autocrlf=true want to strip CRLF down to LF? Shouldn't it? And if so, "blame" is correct to say that you are changing the line endings of all your lines, as what you _would_ commit if you were to commit the tracked files in your working tree would be different from what is in the index, no?

Previous: brian m. carlsonNext: Torsten Bögershausen
Message 6 of 7 in “git blame breaking on repository with CRLF files”
  1. Benkstein, FrankAug 7, 2015
  2. Torsten BögershausenAug 8, 2015
  3. Torsten BögershausenAug 9, 2015
  4. Benkstein, FrankAug 10, 2015
  5. brian m. carlsonAug 10, 2015
  6. Junio C HamanoAug 10, 2015
  7. Torsten BögershausenAug 10, 2015

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.