summaryrefslogtreecommitdiffstats
path: root/blame.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2017-09-25 08:24:06 +0200
committerJunio C Hamano <gitster@pobox.com>2017-09-25 08:24:06 +0200
commitc50424a6f07f17ff9b06927606df650cd73a09a3 (patch)
tree8dad3903bf837ace4c3e05f223004864aead881d /blame.c
parentMerge branch 'ez/doc-duplicated-words-fix' (diff)
parentread_pack_header: handle signed/unsigned comparison in read result (diff)
downloadgit-c50424a6f07f17ff9b06927606df650cd73a09a3.tar.xz
git-c50424a6f07f17ff9b06927606df650cd73a09a3.zip
Merge branch 'jk/write-in-full-fix'
Many codepaths did not diagnose write failures correctly when disks go full, due to their misuse of write_in_full() helper function, which have been corrected. * jk/write-in-full-fix: read_pack_header: handle signed/unsigned comparison in read result config: flip return value of store_write_*() notes-merge: use ssize_t for write_in_full() return value pkt-line: check write_in_full() errors against "< 0" convert less-trivial versions of "write_in_full() != len" avoid "write_in_full(fd, buf, len) != len" pattern get-tar-commit-id: check write_in_full() return against 0 config: avoid "write_in_full(fd, buf, len) < len" pattern
Diffstat (limited to 'blame.c')
0 files changed, 0 insertions, 0 deletions