Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure a consistent line-endings policy #1651

Merged
merged 1 commit into from
May 24, 2024
Merged

Commits on May 23, 2024

  1. Ensure a consistent line-endings policy

    I just went to change one line in a file, then found out the whole file
    changed since it was committed differently to my local system, and we
    don't do normalisation yet. This fixes that.
    
    Here we add a .gitattributes file at the top level with the policy
    `* text=auto` which roughly translates as files that git considers
    "text" are stored internally in history as LF and checked out according
    to local user preference (which might be CRLF on a certain person's
    Win32 box, for example).
    
    In addition to the new .gitattributes, files that had CRLF line-endings
    in the history have been renormalized with `git add --renormalize .`.
    
    This should make cross-platform development easier while respecting
    local configs.
    
    When in Rome...
    ldrumm committed May 23, 2024
    Configuration menu
    Copy the full SHA
    044b280 View commit details
    Browse the repository at this point in the history