summaryrefslogtreecommitdiff
path: root/git/objects/commit.py
diff options
context:
space:
mode:
authorVincent Driessen <me@nvie.com>2016-05-30 16:20:22 +0200
committerVincent Driessen <me@nvie.com>2016-05-30 16:32:26 +0200
commit0eafe201905d85be767c24106eb1ab12efd3ee22 (patch)
tree964391a26b5eefb0289d1d61d0e34740c5c7cecf /git/objects/commit.py
parente836e5cdcc7e3148c388fe8c4a1bab7eeb00cc3f (diff)
downloadgitpython-0eafe201905d85be767c24106eb1ab12efd3ee22.tar.gz
Add test case as example of Git commit with invalid data
This is a real commit from the microjs.com open source project, see https://github.com/madrobby/microjs.com/commit/7e8457c17850d0991763941213dcb403d80f39f8, which is declared to be encoded in UTF-8, but contains invalid bytes. This makes GitPython choke on it while decoding. Rather than choking, this should instead accept the error and replace the invalid bytes by the � (\x80) char.
Diffstat (limited to 'git/objects/commit.py')
0 files changed, 0 insertions, 0 deletions