From: Jim Meyering <jim@meyering.net>
To: git@vger.kernel.org
Subject: Re: [PATCH] git-rev-list: give better diagnostic for failed write
Date: Mon, 25 Jun 2007 23:39:15 +0200 [thread overview]
Message-ID: <87bqf3u324.fsf@rho.meyering.net> (raw)
In-Reply-To: <87r6nzu666.fsf@rho.meyering.net> (Jim Meyering's message of "Mon\, 25 Jun 2007 22\:32\:01 +0200")
Jim Meyering <jim@meyering.net> wrote:
> [this patch depends on the one I posted here:
> http://marc.info/?l=git&m=118280134031923&w=2 ]
Here's a version of that patch that retains the fflush call
and adds a comment explaining why it's needed.
Without this patch, git-rev-list unnecessarily omits strerror(errno)
from its diagnostic, upon write failure:
$ ./git-rev-list --max-count=1 HEAD > /dev/full
fatal: write failure on standard output
With the patch, git reports the desired ENOSPC diagnostic:
fatal: write failure on standard output: No space left on device
* builtin-rev-list (show_commit): Diagnose a failed fflush call.
Signed-off-by: Jim Meyering <jim@meyering.net>
---
builtin-rev-list.c | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/builtin-rev-list.c b/builtin-rev-list.c
index 813aadf..f13a594 100644
--- a/builtin-rev-list.c
+++ b/builtin-rev-list.c
@@ -100,7 +100,12 @@ static void show_commit(struct commit *commit)
printf("%s%c", buf, hdr_termination);
free(buf);
}
- fflush(stdout);
+
+ /* Flush regularly.
+ This is especially important for an asynchronous consumer. */
+ if (fflush(stdout))
+ die("write failure on standard output: %s", strerror(errno));
+
if (commit->parents) {
free_commit_list(commit->parents);
commit->parents = NULL;
next prev parent reply other threads:[~2007-06-25 21:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 20:32 [PATCH] git-rev-list: give better diagnostic for failed write Jim Meyering
2007-06-25 20:59 ` Linus Torvalds
2007-06-25 21:52 ` Jim Meyering
2007-06-25 22:20 ` Linus Torvalds
2007-06-25 22:56 ` Linus Torvalds
2007-06-25 23:01 ` Linus Torvalds
2007-06-27 8:56 ` Jim Meyering
2007-06-25 23:16 ` Linus Torvalds
2007-06-26 17:11 ` Theodore Tso
2007-06-26 17:32 ` Linus Torvalds
2007-06-26 22:04 ` Theodore Tso
2007-06-26 22:32 ` Linus Torvalds
2007-06-28 19:04 ` Theodore Tso
2007-06-28 21:34 ` Jeff King
2007-06-28 23:53 ` [PATCH] Don't fflush(stdout) when it's not helpful Theodore Tso
2007-06-29 1:05 ` Frank Lichtenheld
2007-06-29 3:48 ` Theodore Tso
2007-06-29 6:38 ` Jeff King
2007-06-29 7:07 ` Junio C Hamano
2007-06-29 16:06 ` Linus Torvalds
2007-06-29 17:40 ` Theodore Tso
2007-06-29 23:43 ` Linus Torvalds
2007-06-30 2:15 ` Junio C Hamano
2007-06-30 4:24 ` Linus Torvalds
2007-06-30 14:27 ` Theodore Tso
2007-06-30 18:42 ` Junio C Hamano
2007-06-26 9:06 ` [PATCH] git-rev-list: give better diagnostic for failed write Jeff King
2007-06-26 17:12 ` Linus Torvalds
2007-06-27 8:59 ` Jim Meyering
2007-06-27 16:06 ` Linus Torvalds
2007-06-25 21:39 ` Jim Meyering [this message]
2007-06-25 21:53 ` Linus Torvalds
2007-06-25 22:08 ` Jim Meyering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bqf3u324.fsf@rho.meyering.net \
--to=jim@meyering.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).