Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork960
Fix bug in diff parser output#454
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
The diff --patch parser was missing some edge case where Git wouldencode non-ASCII chars in path names as octals, but these weren'tdecoded properly. \360\237\222\251.txtDecoded via utf-8, that will return: 💩.txt
cc1c258 to1faf84fComparenvie commentedMay 30, 2016
@Byron This is a bug we've seen in production for some time now. Happy for me to release 2.0.4 with this fix right now? |
Byron commentedMay 30, 2016
No objections, please feel free to make a release. In any case, thanks for your contribution :) ! |
nvie commentedMay 30, 2016
Sure, will do! |
nvie commentedMay 30, 2016
2.0.4 is now up on PyPI :) |
The diff
--patchoutput parser was missing some edge case where Git would encode non-ASCII chars in path names as octals, but these weren't decoded properly.Decoded via utf-8, that will return: