| commit | 384f122b7c6dd2b52cc6029afee16560c38850ae | |
| author | Jim Meyering <jim@meyering.net> | |
| Sun, 24 Jun 2007 19:13:11 +0000 (24 21:13 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 27 Jun 2007 04:49:44 +0000 (26 21:49 -0700) | ||
| tree | 9598c14697f8c7ce04eb2816f98e34f743c4cd5d | treesnapshot (tar.gz zip) |
| parent | 91c8d5905c33e9d7c9014a1c6c7cec8eb86584df | commitdiff |
Don't ignore a pack-refs write failure
Without this, if the size of refs_file at that point is ever an exact
multiple of BUFSIZ, then an EIO or ENOSPC error on the final write would
not be diagnosed.
It's not worth worrying about EPIPE here.
Although theoretically possible that someone kill this process
with a manual SIGPIPE, it's not at all likely.
Signed-off-by: Jim Meyering <jim@meyering.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Without this, if the size of refs_file at that point is ever an exact
multiple of BUFSIZ, then an EIO or ENOSPC error on the final write would
not be diagnosed.
It's not worth worrying about EPIPE here.
Although theoretically possible that someone kill this process
with a manual SIGPIPE, it's not at all likely.
Signed-off-by: Jim Meyering <jim@meyering.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin-pack-refs.c | diffblobblamehistory |