Re: Consequences of CRLF in index?

From: Johannes Sixt <j6t@kdbg.org>
Date: Oct 24, 2017, 21:04 UTC
Message-ID: <eda48d5e-a52c-9a39-8e55-a6828efdb3ef@kdbg.org>
In-Reply-To: <D0A67AD8-2D63-4683-9F2A-20B0E8E65D4B@gmail.com>

Am 24.10.2017 um 19:48 schrieb Lars Schneider:

Show 6 quoted lines

> I've migrated a large repo (110k+ files) with a lot of history (177k commits)
> and a lot of users (200+) to Git. Unfortunately, all text files in the index
> of the repo have CRLF line endings. In general this seems not to be a problem
> as the project is developed exclusively on Windows.
> 
> However, I wonder if there are any "hidden consequences" of this setup?

I've been working on a project with CRLF in every source file for a decade now. It's C++ source, and it isn't even Windows-only: when checked out on Linux, there are CRs in the files, with no bad consequences so far. GCC is happy with them.

-- Hannes

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.