Restore leading spaces on empty context lines in patch files #2015
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
pali6
force-pushed
the
patch-restore-leading-space
branch
from
6b704ef to
abd464d
Compare
git apply generally does not care, except for CRLF line endings with CRLF line endings if an empty line in the patch context does not have a leading space it results in a "corrupt patch" error
pali6
force-pushed
the
patch-restore-leading-space
branch
from
abd464d to
13edda7
Compare
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.
Usually
git applydoes not care about these. However, if the repository is checked out with CRLF line endings, an empty line in the patch context without a leading space results in a "corrupt patch" error. In other cases this change should have no effect.