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

git blame swallows up lines in case of mixed line endings

From
SESokolov, Konstantin (ext) <konstantin.sokolov.ext@siemens.com>
Date
Feb 19, 2015, 13:48 UTC
Message-ID
<71BF70CE41AEE741896AF3A5450D86F11F2D1F46@DEFTHW99EH3MSX.ww902.siemens.net>
Hi Folks,
I encounter unexpected behavior in the following case:
file content:

line1<CR><LF> line2<CR> line3<CR><LF> line4

This is what I get as console output (on Windows):
> git blame -s file.txt

7db36436 1) line1 line3436 2) line2 7db36436 3) line4

This is the real content:
> git blame -s file.txt > blame.txt
blame.txt opened in Notepad++:

7db36436 1) line1 <CR><LF> 7db36436 2) line2 <CR> line3 <CR><LF> 7db36436 3) line4 <LF>

Admittedly, very stupid editors, such as Windows Notepad, cannot handle mixed line endings as well. But is this also the way git blame should behave?

Kind regards Konstantin

Next: Torsten Bögershausen
Message 1 of 6 in “git blame swallows up lines in case of mixed line endings”
  1. Sokolov, Konstantin (ext)Feb 19, 2015
  2. Torsten BögershausenFeb 21, 2015
  3. AW: git blame swallows up lines in case of mixed line endingsSokolov, Konstantin (ext), Feb 23, 2015
  4. Junio C HamanoFeb 23, 2015
  5. AW: git blame swallows up lines in case of mixed line endingsSokolov, Konstantin (ext), Feb 23, 2015
  6. Junio C HamanoFeb 23, 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.