From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Martin Langhoff'" <martin.langhoff@gmail.com>,
"'brian m. carlson'" <sandals@crustytoothpaste.net>,
"'Git Mailing List'" <git@vger.kernel.org>
Subject: RE: osx autocrlf sanity?
Date: Wed, 10 Jun 2020 09:59:34 -0400 [thread overview]
Message-ID: <027001d63f2f$622f2d00$268d8700$@nexbridge.com> (raw)
In-Reply-To: <CACPiFCKEGXK+TJtQiPub3dW6dYKJ7a=mXL+UCDP57N-3XtRYLg@mail.gmail.com>
On June 10, 2020 9:55 AM, Martin Langhoff wrote:
> To: brian m. carlson <sandals@crustytoothpaste.net>; Martin Langhoff
> <martin.langhoff@gmail.com>; Git Mailing List <git@vger.kernel.org>
> Subject: Re: osx autocrlf sanity?
>
> On Tue, Jun 9, 2020 at 8:04 PM brian m. carlson
> <sandals@crustytoothpaste.net> wrote:
> > On 2020-06-09 at 23:31:23, Martin Langhoff wrote:
> > > good question! There is a .gitattributes file, all the files
> > > affected have these attributes
> > >
> > > *.py text diff=python
> >
> > By default, Git will check out files with the text attribute with the
> > native line ending, and it will check them in with LF endings. That
> > can be controlled by core.eol and core.autocrlf
>
> Why is core.autocrlf false not working for me?
>
> I want to work on a repo that has a mix of newlines. I'd like git to completely
> ignore them. Treat all files as a bag'o'bytes.
>
> Assume I am running git rebase over commits that have .gitattributes, so I
> can't "just remove it".
We use core.autocrlf=input on all our platforms for source files, including OSX.
Does that work for you?
Regards,
Randall
-- Brief whoami:
NonStop developer since approximately 211288444200000000
UNIX developer since approximately 421664400
-- In my real life, I talk too much.
next prev parent reply other threads:[~2020-06-10 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 19:52 osx autocrlf sanity? Martin Langhoff
2020-06-09 23:13 ` brian m. carlson
2020-06-09 23:31 ` Martin Langhoff
2020-06-10 0:03 ` brian m. carlson
2020-06-10 13:55 ` Martin Langhoff
2020-06-10 13:59 ` Randall S. Becker [this message]
2020-06-10 14:19 ` Martin Langhoff
2020-06-10 23:53 ` brian m. carlson
2020-06-10 14:34 ` Torsten Bögershausen
2020-06-10 14:51 ` Martin Langhoff
2020-06-10 17:06 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='027001d63f2f$622f2d00$268d8700$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
--cc=sandals@crustytoothpaste.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).