summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>2007-06-24 19:13:11 (GMT)
committerJunio C Hamano <gitster@pobox.com>2007-06-27 04:49:44 (GMT)
commit384f122b7c6dd2b52cc6029afee16560c38850ae (patch)
tree9598c14697f8c7ce04eb2816f98e34f743c4cd5d /README
parent91c8d5905c33e9d7c9014a1c6c7cec8eb86584df (diff)
downloadgit-384f122b7c6dd2b52cc6029afee16560c38850ae.zip
git-384f122b7c6dd2b52cc6029afee16560c38850ae.tar.gz
git-384f122b7c6dd2b52cc6029afee16560c38850ae.tar.bz2
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>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions