Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | patch_parse: allow parsing ambiguous patch headers | Patrick Steinhardt | 2017-11-11 | 1 | -0/+6 |
| | | | | | | | | | | | | | | | The git patch format allows for having unquoted paths with whitespaces inside. This format becomes ambiguous to parse, e.g. in the following example: diff --git a/file b/with spaces.txt b/file b/with spaces.txt While we cannot parse this in a correct way, we can instead use the "---" and "+++" lines to retrieve the file names, as the path is not followed by anything here but spans the complete remaining line. Because of this, we can simply bail outwhen parsing the "diff --git" header here without an actual error and then proceed to just take the paths from the other headers. | ||||
* | patch: differentiate not found and invalid patches | Edward Thomson | 2016-05-26 | 1 | -6/+75 |
| | |||||
* | git_patch_parse_ctx: refcount the context | Edward Thomson | 2016-05-26 | 1 | -0/+1 |
| | |||||
* | patch: `git_patch_from_patchfile` -> `git_patch_from_buffer` | Edward Thomson | 2016-05-26 | 1 | -1/+2 |
| | |||||
* | Introduce git_patch_options, handle prefixes | Edward Thomson | 2016-05-26 | 1 | -3/+5 |
| | | | | | Handle prefixes (in terms of number of path components) for patch parsing. | ||||
* | patch_parse: ensure we can parse a patch | Edward Thomson | 2016-05-26 | 1 | -0/+31 |