summaryrefslogtreecommitdiff
path: root/src/commit.c
diff options
context:
space:
mode:
authorPatrick Steinhardt <ps@pks.im>2019-10-18 12:33:07 +0200
committerPatrick Steinhardt <ps@pks.im>2019-10-18 13:29:36 +0200
commit7968e90f79d4c209f26d6a6f48db2137b168906e (patch)
treeb331ea71173cfa9b8c3c884d5cccb7a064c5bfd4 /src/commit.c
parent8532ed11848092d816aecc2d34d1bb432a525df9 (diff)
downloadlibgit2-7968e90f79d4c209f26d6a6f48db2137b168906e.tar.gz
refdb_fs: properly parse corrupted reflogs
In previous versions, libgit2 could be coerced into writing reflog messages with embedded newlines into the reflog by using `git_stash_save` with a message containing newlines. While the root cause is fixed now, it was noticed that upstream git is in fact able to read such corrupted reflog messages just fine. Make the reflog parser more lenient in order to just skip over malformatted reflog lines to bring us in line with git. This requires us to change an existing test that verified that we do indeed _fail_ to parse such logs.
Diffstat (limited to 'src/commit.c')
0 files changed, 0 insertions, 0 deletions