Re: osx autocrlf sanity?

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Jun 10, 2020, 23:53 UTC
Message-ID: <20200610235337.GW6569@camp.crustytoothpaste.net>
In-Reply-To: <CACPiFCKEGXK+TJtQiPub3dW6dYKJ7a=mXL+UCDP57N-3XtRYLg@mail.gmail.com>

On 2020-06-10 at 13:55:12, Martin Langhoff wrote:

Show 13 quoted lines

> 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?

core.autocrlf to false means that it is disabled and has no effect. core.eol defaults to "lf" on Unix systems and "crlf" on Windows, and is used even when core.autocrlf is disabled.

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

Then you need to use plumbing commands like git cat-file. You could also write a .git/info/attributes file that contains the following:

    *.py !text

or

    * !text

which will override the file in the repository.

-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204