README: Fixing eol from CRLF to LF #66
Closed
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
Member
|
Is this the only file affected? |
Member
Author
|
Git status looks calm now. |
Member
Author
|
That was my status right after cloning the repo:
I also tried to clone it again, checking if it was a git error. |
Member
Author
|
@scottgonzalez, you can close this one as you're going to do a fresh clone and commit in every jQuery repos. |
Member
|
Fixed in 10913e0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
I've just forked and cloned this repo today and saw that git already pointed a diff in its status.
It checked README.md that had CRLF line endings. This probably occurred after @1cbb978 when it was set a defaul eol in
.gitattributes.To stop my personal pain I converted the EOL from CRLF (Windows) to LF (Unix). That's the only change in this commit.