projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: e4d9516) | patch
sha1_file.c (write_sha1_from_fd): Detect close failure.
authorJim Meyering <jim@meyering.net>
Mon, 26 Mar 2007 13:57:23 +0000 (15:57 +0200)
committerJunio C Hamano <junkio@cox.net>
Tue, 27 Mar 2007 19:43:49 +0000 (12:43 -0700)
commit0d315468f38729ebb15711349cece98a467032c9
tree40184f1d72e66267e82a570c7c27568cbba347fbtree | snapshot
parente4d9516b2196623d927e232b4e8766269a837fe6commit | diff
sha1_file.c (write_sha1_from_fd): Detect close failure.

I stumbled across this in the context of the fchmod 0444 patch.
At first, I was going to unlink and call error like the two subsequent
tests do, but a failed write (above) provokes a "die", so I made
this do the same.  This is testing for a write failure, after all.

Signed-off-by: Jim Meyering <jim@meyering.net>
Signed-off-by: Junio C Hamano <junkio@cox.net>
sha1_file.c diff | blob | history
Git—the stupid content tracker