Change Details

ac5f7be6a8688955a282becf00eebc542238a86b enforced new EOL settings on files via `.gitattributes`. According to [git documentation](https://docs.github.com/en/get-started/getting-started-with-git/configuring-git-to-handle-line-endings#refreshing-a-repository-after-changing-line-endings) doing so requires normalizing the line endings as the git index isn't automatically refreshed from `.gitattributes` changes. This patch is the output of `git add --renormalize .` on main. We saw this issue because our automation performed a `chown` which changed the timestamp and manifested diffs where none were expected. N.B. this only affects what exists inside the git index, not what's on disk which will go through filters to get the correct line endings. Testing: ninja check-all

Git wants to check in 'text' files with LF endings, so this changes them in the repository but not in the checkout, where they keep CRLF endings.

ac5f7be6a8688955a282becf00eebc542238a86b enforced new EOL settings on files via `.gitattributes`. According to [git documentation](https://docs.github.com/en/get-started/getting-started-with-git/configuring-git-to-handle-line-endings#refreshing-a-repository-after-changing-line-endings) doing so requires normalizing the line endings as the git index isn't automatically refreshed from `.gitattributes` changes. This patch is the output of `git add --renormalize .` on main. We saw this issue because our automation performed a `chown` which changed the timestamp and manifested diffs where none were expected. N.B. this only affects what exists inside the git indexGit wants to check in 'text' files with LF endings, not what's on disk which will go through filters to get the correct line endings. Testing:so this changes them ninjain the repository but not in the check-allkout, where they keep CRLF endings.