Forcing old images to not be CRLF conformed due to new gitattributes file #1182
Conversation
This file contains 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
|
It makes sense. Looks good to me |
mohsen1
added a commit
that referenced
this pull request
Apr 18, 2015
Forcing old images to not be CRLF conformed due to new gitattributes file
vincent-zurczak
pushed a commit
to roboconf/swagger-ui
that referenced
this pull request
Aug 19, 2016
Forcing old images to not be CRLF conformed due to new gitattributes file
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.
This was breaking an automated build process in drupal via drush: No longer able to automatically change branches because the LF was inserted in place of CRLF in binary files? Screenshot is from my fork, but it was without modification (until this PR). Our project is temporarily building from my fork until we find a better resolution.
mac osx git version 2.3.2 (Apple Git-55) (same issue on centos box however)