distinguish error versus short read from read_in_full()
commit41dcc4dcccecca49e3f75212ce9e614ffe2bdcc8
authorJeff King <peff@peff.net>
Wed, 27 Sep 2017 06:02:11 +0000 (27 02:02 -0400)
committerJunio C Hamano <gitster@pobox.com>
Wed, 27 Sep 2017 06:45:24 +0000 (27 15:45 +0900)
tree1511cf57f1762ba21bc920a85239063a16e7de91
parent90dca6710e6e5aad5d78d0cd006c3adadb65524d
distinguish error versus short read from read_in_full()

Many callers of read_in_full() expect to see the exact
number of bytes requested, but their error handling lumps
together true read errors and short reads due to unexpected
EOF.

We can give more specific error messages by separating these
cases (showing errno when appropriate, and otherwise
describing the short read).

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
builtin/get-tar-commit-id.c
bulk-checkin.c
packfile.c