From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Bryan Turner <bturner@atlassian.com>,
Git Mailing list <git@vger.kernel.org>
Subject: Re: what is git's position on "classic" mac <CR>-only end of lines?
Date: Sun, 1 Oct 2017 17:29:58 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1710011723360.27763@localhost.localdomain> (raw)
In-Reply-To: <a8cb7c82-4598-5dce-0e0e-b0f18157cc56@kdbg.org>
On Sun, 1 Oct 2017, Johannes Sixt wrote:
> Am 01.10.2017 um 21:29 schrieb Bryan Turner:
> > On Sun, Oct 1, 2017 at 10:52 AM, Robert P. J. Day <rpjday@crashcourse.ca>
> > 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" ;)
that's fine, that's all i was after -- basically, git handles Mac OS
X and macOS, and if you're dealing with mac "classic" EOLs, well ...
http://i.imgur.com/z96dZ0x.jpg
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2017-10-01 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 17:52 what is git's position on "classic" mac <CR>-only end of lines? Robert P. J. Day
2017-10-01 19:29 ` Bryan Turner
2017-10-01 20:58 ` Johannes Sixt
2017-10-01 21:29 ` Robert P. J. Day [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.21.1710011723360.27763@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=bturner@atlassian.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).