Consequences of CRLF in index?

Hi,

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? If there are consequences, then I see two options. Either I rebase the repo and fix the line endings for all commits or I add a single commit that fixes the line endings for all files. Both actions require coordination with the users to avoid repo trouble/merge conflicts. The "single fixup commit" options would also make diffs into the past look bad. Would a single large commit have any impact on the performance of standard Git operations?

Thanks, Lars