Cleanup: file permissions and line endings. #1498
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
All those file patterns are not strictly needed. They just prevent git from guessing.
|
BTW, you can regenerate last commit by touching all files and commiting the result. |
ffissore
pushed a commit
that referenced
this pull request
Sep 27, 2013
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.
It does 2 things:
Second change - splitted into 2 commits - had to "rewrite" 294 files. It will probably bring some problems with merging, but they can be solved (*) by merging with git merge -s recursive -Xrenormalize (or -Xignore-space-at-eol or -Xignore-space-change)
( * http://stackoverflow.com/questions/861995/is-it-possible-for-git-merge-to-ignore-line-ending-differences )