Add literal binary patch support #4
Draft
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.
What's changed?
Added support for generation of Git binary patches using the literal format style.
What's your motivation?
There is a need to support representing binary files within a patch file.
Anything in particular you'd like reviewers to focus on?
This diverges us from upstream JGit which does not support writing Git binary patch files at all (it does support reading and applying them). The changes are minimally invasive, but would pose merge conflicts against the upstream. This probably isn't a large concern given we're needing to support Java 8+ (thus the reason for forking the project originally).
Anyone you would like to review specifically?
Anybody
Have you considered any alternatives or workarounds?
We could externalize the changes into new classes or place these updates further downstream in rewrite proper, but this felt like the right place to at least get started with a review.
Any additional context
N/A
Checklist