From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: osx autocrlf sanity?
Date: Tue, 9 Jun 2020 23:13:36 +0000 [thread overview]
Message-ID: <20200609231336.GQ6569@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CACPiFCJKvnDL9Xj1Xs0RCvuhymjDz4N0hT42dNtBQxp+TLiPaw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On 2020-06-09 at 19:52:42, Martin Langhoff wrote:
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2020-06-09 23:14 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 [this message]
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
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=20200609231336.GQ6569@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
/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).