set file encoding and line separator#122
Open
eric-milles wants to merge 1 commit into
Open
Conversation
Member
Author
|
@maartenc Any issues with this? |
Contributor
|
At first sight, I would say:
But my focus is now on the 2.6.0 release. |
eric-milles
force-pushed
the
encoding-and-ending
branch
from
4ea9edc to
2ccc0be
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fix the warning for no project encoding. There were 2 stray chars in ResolveTest. And set line endings so carriage returns don't keep trickling in.