-
Notifications
You must be signed in to change notification settings - Fork 71
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
git diff adding a new empty file is not parsed correctly #19
Comments
I see, you're right, will take a look. |
This is a problem for any changes to binary files. Capturing these changes in the metadata and being able to iterate over them as part of the PatchSet would be great. |
fwiw a while ago i made a start on a diff/patch parser. i just published that w-i-p code here: https://github.com/wbolster/diffparse it tries to get metadata from svn and git diffs |
sample output from that parser (see
|
This is needed to fix a bug with it not noticing new empty files being added. The fix first appears in v0.7.1[[1]] [[2]] It was reported in the pip project[[3]]. [1]: matiasb/python-unidiff#19 [2]: matiasb/python-unidiff#86 [3]: pypa/pip#11969
a git diff adding a new empty file is not parsed correctly. the patch set contains 0 items in that case, while it should contain one.
sample:
diff --git a/empty b/empty new file mode 100644 index 0000000..e69de29
The text was updated successfully, but these errors were encountered: