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

Re: AW: git blame swallows up lines in case of mixed line endings

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 23, 2015, 20:27 UTC
Message-ID
<xmqqmw44s794.fsf@gitster.dls.corp.google.com>
In-Reply-To
<71BF70CE41AEE741896AF3A5450D86F11F2D21EB@DEFTHW99EH3MSX.ww902.siemens.net>

"Sokolov, Konstantin (ext)" <konstantin.sokolov.ext@siemens.com> writes:

> Thank you for going into the matter. I was not aware of the textconv
> filter. This is definitely a decent solution. But what exactly do you
> mean by "Even though we have an option to mark <CR> alone as the end
> of line marker"?
s/have/do not have/; sorry for a false hope ;-)
Previous: Sokolov, Konstantin (ext)
Message 6 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.