Re: osx autocrlf sanity?

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Jun 10, 2020, 13:55 UTC
Message-ID: <CACPiFCKEGXK+TJtQiPub3dW6dYKJ7a=mXL+UCDP57N-3XtRYLg@mail.gmail.com>
In-Reply-To: <20200610000358.GR6569@camp.crustytoothpaste.net>

On Tue, Jun 9, 2020 at 8:04 PM brian m. carlson <sandals@crustytoothpaste.net> wrote:

Show 9 quoted lines

> 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".

regards,

-- 
 martin.langhoff@gmail.com
 - ask interesting questions  ~  http://linkedin.com/in/martinlanghoff
 - don't be distracted        ~  http://github.com/martin-langhoff
   by shiny stuff