Unify line ending to unix-style #41
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Weird. I think the gitattributes approach is the simplest for now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
[No content change, just EOL encoding CRLF -> LF. Other rust files are already LF 🤷]
(Reported on the package review for Fedora. This is relevant because the
.rsfiles are actually packaged and available in the*-develpackage. Not crucial though, so no need for a bug fix release for this one.)There are 2 ways to enforce consistency:
.gitattributesWhich one would you prefer? With the former the End-Of-File can also be enforced since I see that one is also not fully consistent.