Revision 96c6bb566ee5354a1b07530a94d3f85055e46032 authored by Junio C Hamano on 23 October 2017, 05:37:21 UTC, committed by Junio C Hamano on 23 October 2017, 05:37:22 UTC
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
| File | Mode | Size |
|---|---|---|
| bitmap.c | -rw-r--r-- | 4.9 KB |
| ewah_bitmap.c | -rw-r--r-- | 16.1 KB |
| ewah_io.c | -rw-r--r-- | 5.3 KB |
| ewah_rlw.c | -rw-r--r-- | 2.9 KB |
| ewok.h | -rw-r--r-- | 6.5 KB |
| ewok_rlw.h | -rw-r--r-- | 3.1 KB |
Computing file changes ...
