On June 10, 2020 9:55 AM, Martin Langhoff wrote: > To: brian m. carlson <sandals@xxxxxxxxxxxxxxxxxxxx>; Martin Langhoff > <martin.langhoff@xxxxxxxxx>; Git Mailing List <git@xxxxxxxxxxxxxxx> > Subject: Re: osx autocrlf sanity? > > On Tue, Jun 9, 2020 at 8:04 PM brian m. carlson > <sandals@xxxxxxxxxxxxxxxxxxxx> 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.
