Fixed two more places where SVN/unified diff really wants a tab instead of spaces #14
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
…ad of spaces: before (revision $REV) and (working copy).
jwiegley
added a commit
that referenced
this pull request
Oct 17, 2012
Fixed two more places where SVN/unified diff really wants a tab instead of spaces
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.
Those places being before (revision $REV) and (working copy).
I found more people having trouble applying patches created with git-svn-diff using TortoiseSVN. Manually changing the spaces before (revision XXX) and (working copy) was enough to make the patches work for both TortoiseSVN 1.6 and 1.7. TortoiseSVN itself puts a single tab in both of those locations, as does Gnu diff -u.