summaryrefslogtreecommitdiff
path: root/tests/apply
Commit message (Collapse)AuthorAgeFilesLines
* git_patch_parse_ctx: refcount the contextEdward Thomson2016-05-261-0/+1
|
* patch: `git_patch_from_patchfile` -> `git_patch_from_buffer`Edward Thomson2016-05-261-12/+13
|
* apply: test postimages that grow/shrink originalEdward Thomson2016-05-261-0/+42
| | | | | | | Test with some postimages that actually grow/shrink from the original, adding new lines or removing them. (Also do so without context to ensure that we can add/remove from a non-zero part of the line vector.)
* Introduce git_patch_options, handle prefixesEdward Thomson2016-05-261-37/+37
| | | | | Handle prefixes (in terms of number of path components) for patch parsing.
* apply: move patch data to patch_common.hEdward Thomson2016-05-263-576/+2
|
* patch: abstract patches into diff'ed and parsedEdward Thomson2016-05-261-0/+1
| | | | | | Patches can now come from a variety of sources - either internally generated (from diffing two commits) or as the results of parsing some external data.
* patch parsing: ensure empty patches are illegalEdward Thomson2016-05-261-0/+8
|
* patch parsing: parse binary patch filesEdward Thomson2016-05-261-55/+123
|
* patch application: apply binary patchesEdward Thomson2016-05-263-11/+242
| | | | | | Handle the application of binary patches. Include tests that produce a binary patch (an in-memory `git_patch` object), then enusre that the patch applies correctly.
* apply: handle empty patchesEdward Thomson2016-05-261-0/+8
| | | | When a patch is empty, simply copy the source into the destination.
* Patch parsing from patch filesEdward Thomson2016-05-262-0/+490
|
* Introduce git_apply_patchEdward Thomson2016-05-262-0/+462
The beginnings of patch application from an existing (diff-created) git_patch object: applies the hunks of a git_patch to a buffer.