Actually normallise the End of Lines #27
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
Really reset the eol's in the repository by following the info at git-scm.com/docs/gitattributes Following the example there the following commands were run: rm .git/index git reset git add -u git commit
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.
I thought that the sequence of commands I did for the pull request #19 worked
However apparently it doesn't do all the files, only some which are checked out for those specific commits.
So to really reset the eols I followed the example at
git-scm.com/docs/gitattributes
and ran the following commands:
that forces the index to be rebuilt and so all the line endings which could change do get changed.
I also removed the
textsections fromtext eol=crlfsince they are not neededYou could also do the same for the https://github.com/sshnet/Cryptography repository to fix the same there.
Sorry about the mix up.