Re: [PATCH 0/2] submodule add + autocrlf + safecrlf
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 20, 2012, 17:49 UTC
- Message-ID
- <7vipelx49g.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <cover.1340202515.git.brad.king@kitware.com>
Brad King <brad.king@kitware.com> writes:
Show 10 quoted lines
> When 'git submodule add' uses 'git config' to create a > '.gitmodules' file it gets LF newlines that the subsequent > 'git add --force .gitmodules' rejects if autocrlf and > safecrlf are both enabled. This series adds a test and > proposes a fix that simply uses '-c core.safecrlf=false' > to disable safecrlf when adding '.gitmodules'. > > I'm not excited by allowing a LF file in work tree that > has clearly been configured to prefer CRLF, but avoiding > that for .gitmodules is probably a separate issue.
I have a suspicion that "git config" should be taught about this kind of thing instead.
Shoudn't your .git/config file that is outside the revision control also end with CRLF if your platform and project prefer CRLF over LF?