Web lists-archives.com

Re: what is git's position on "classic" mac <CR>-only end of lines?




Am 01.10.2017 um 21:29 schrieb Bryan Turner:
On Sun, Oct 1, 2017 at 10:52 AM, Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote:

   sorry for more pedantic nitpickery, but i'm trying to write a
section on how to properly process mixtures of EOLs in git, and when i
read "man git-config", everything seems to refer to Mac OS X and macOS
(and linux, of course) using <LF> for EOL, with very little mention of
what one does if faced with "classic" mac EOL of just <CR>.

  No command in Git that I'm aware of considers a standalone <CR> to be
a line ending. A file containing only <CR>s is treated as a single
line by every Git command I've used. I'm not sure whether that
behavior is configurable. For files with standalone <CR>s mixed with
other line endings (<CRLF> or <LF>, either or both), the <CRLF> and
<LF> endings are both considered line endings while the standalone
<CR>s are not.

That's true, AFAIK. In addition, when Git auto-detects whether a file is binary or text, then a file with a bare CR is treated as binary:

https://github.com/git/git/blob/master/convert.c#L91

That basically amounts to: "it [is] considered not important enough to deal with" ;)

-- Hannes