Re: osx autocrlf sanity?
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- Jun 9, 2020, 23:13 UTC
- Message-ID
- <20200609231336.GQ6569@camp.crustytoothpaste.net>
- In-Reply-To
- <CACPiFCJKvnDL9Xj1Xs0RCvuhymjDz4N0hT42dNtBQxp+TLiPaw@mail.gmail.com>
On 2020-06-09 at 19:52:42, Martin Langhoff wrote:
Show 21 quoted lines
> Hi git list, > > long time no see! I am here to ask for a sanity check. I'm on OSX. > Checking out a repository that has an un-controlled mix of line > endings. Mostly linux-style, but some Windows CRLF endings. > > A few tests. > - I set core.autocrlf=input globally --> a fresh clone doesn't have a > clean status files look modified right after a clone) > - set core.autocrlf=false globally --> a fresh clone doesn't have a > clean status > - set core.autocrlf=true globally --> a fresh clone doesn't have a clean status > > This is git v2.23.0 from Homebrew. > > Am I doing something wrong? Can git work sanely on a mixed endings > repo without having to fix the world first? > > ... I do strive to fix the world (and this small repository), as we > all do, but it should not be a preconditions before git behaves > sanely.
Does this repository have a .gitattributes file and if so, is there any correlation between the patterns in that file and the modified files?
-- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204