summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorPatrick Steinhardt <ps@pks.im>2019-07-05 11:06:33 +0200
committerPatrick Steinhardt <ps@pks.im>2019-07-11 12:11:11 +0200
commit3f855fe863e7260ea4b7bc36a0c78ea2bff37b68 (patch)
treec6fed7a801144713282860976ed1cd66510957d9 /include
parentb30dab8fa7e1c2d6bd938cd5941c9d1cd55a0004 (diff)
downloadlibgit2-3f855fe863e7260ea4b7bc36a0c78ea2bff37b68.tar.gz
patch_parse: handle missing newline indicator in old file
When either the old or new file contents have no newline at the end of the file, then git-diff(1) will print out a "\ No newline at end of file" indicator. While we do correctly handle this in the case where the new file has this indcator, we fail to parse patches where the old file is missing a newline at EOF. Fix this bug by handling and missing newline indicators in the old file. Add tests to verify that we can parse such files.
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions