From: Jeff King <peff@peff.net>
To: Jonas Fonseca <jonas.fonseca@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [tig PATCH] continue updates when pipe read has errno "Success"
Date: Fri, 22 Aug 2008 11:59:14 -0400 [thread overview]
Message-ID: <20080822155914.GB5280@coredump.intra.peff.net> (raw)
In-Reply-To: <2c6b72b30808220310v1083e860tef9fd6efa57767e3@mail.gmail.com>
On Fri, Aug 22, 2008 at 12:10:35PM +0200, Jonas Fonseca wrote:
> Thanks for the fix/workaround!
Thank you for making tig. ;)
> For a possible "better" fix, I have been working on moving tig to use
> the run-command.[ch] code from git, which means that ferror() will no
> longer be needed. It is still not ready but looks promising.
I think that would be much cleaner, as the semantics of system calls and
signals tend to be better defined.
-Peff
prev parent reply other threads:[~2008-08-22 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 1:40 [tig PATCH] continue updates when pipe read has errno "Success" Jeff King
2008-08-22 10:10 ` Jonas Fonseca
2008-08-22 15:59 ` Jeff King [this message]
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=20080822155914.GB5280@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=jonas.fonseca@gmail.com \
/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).