Force shell scripts to keep their Unix line termination #96
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On Unix systems, running a shell script with DOS line terminations
(CRLF) fails because the system attempts to execute whatever is on
the shebang, including the "\r" preceding the "\n".
For some reason, the rust-src tarball's install.sh started having CRLF
line endings starting June 29 on nightly (betas are affected as well).
This makes the install.sh file they contain non-executable.
The rust code that creates install.sh from install-template.sh doesn't
seem to do anything that would affect line terminations. So it seems
what might be happening is that those tarballs are now created on a
Windows machine, and the CRLFs slip in from autoconversion by git.
This .gitattributes should prevent such autoconversion.