From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Clean up file descriptors when calling hooks.
Date: Wed, 07 Dec 2005 18:25:12 -0800 [thread overview]
Message-ID: <7vvey0mik7.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0512072052560.25300@iabervon.org> (Daniel Barkalow's message of "Wed, 7 Dec 2005 21:04:38 -0500 (EST)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> When calling post-update hook, don't leave stdin and stdout connected to
> the pushing connection.
A quick question. I understand "not connected to the pushing
connection" is desirable, but is there a reason you chose to
leave them open to /dev/null, not close()d?
next prev parent reply other threads:[~2005-12-08 2:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 2:04 [PATCH] Clean up file descriptors when calling hooks Daniel Barkalow
2005-12-08 2:25 ` Junio C Hamano [this message]
2005-12-08 5:33 ` Daniel Barkalow
2005-12-08 5:40 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2005-12-08 3:24 linux
2005-12-08 3:29 ` Junio C Hamano
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=7vvey0mik7.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=barkalow@iabervon.org \
--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).