From: Tay Ray Chuan <rctay89@gmail.com>
To: Yuval Kogman <nothingmuch@woobling.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Don't try to reclose in command_close_bidi_pipe
Date: Fri, 30 Jan 2009 22:35:54 +0800 [thread overview]
Message-ID: <be6fef0d0901300635v4e6009f1n7da405ebc4c8dd68@mail.gmail.com> (raw)
In-Reply-To: <1233291570-23295-1-git-send-email-nothingmuch@woobling.org>
Hi,
On Fri, Jan 30, 2009 at 12:59 PM, Yuval Kogman <nothingmuch@woobling.org> wrote:
> Some commands require their standard input to be closed (like
> git-commit-tree). This patch changes command_close_bidi_pipe so no
> longer tries to close already closed handles, resulting in an error.
>From this message, you seem to intend this as a fix. Can you tell us
how one might go about to reproduce this issue?
> ---
> perl/Git.pm | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/perl/Git.pm b/perl/Git.pm
> index 7d7f2b1..283bba8 100644
> --- a/perl/Git.pm
> +++ b/perl/Git.pm
> @@ -422,6 +422,7 @@ sub command_close_bidi_pipe {
> local $?;
> my ($pid, $in, $out, $ctx) = @_;
> foreach my $fh ($in, $out) {
> + next unless defined(fileno($fh));
Quoting the perldoc for fileno at http://perldoc.perl.org/functions/fileno.html
"(Filehandles connected to memory objects via new features of open may
return undefined even though they are open.)"
Is "unless defined(fileno($fh))" a reliable way to check if the handle
is closed?
--
Cheers,
Ray Chuan
next prev parent reply other threads:[~2009-01-30 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 4:59 [PATCH] Don't try to reclose in command_close_bidi_pipe Yuval Kogman
2009-01-30 14:35 ` Tay Ray Chuan [this message]
2009-01-30 15:06 ` Yuval Kogman
2009-01-31 0:03 ` Tay Ray Chuan
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=be6fef0d0901300635v4e6009f1n7da405ebc4c8dd68@mail.gmail.com \
--to=rctay89@gmail.com \
--cc=git@vger.kernel.org \
--cc=nothingmuch@woobling.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).