From: Paul Serice <paul@serice.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Run hooks with a cleaner environment
Date: Tue, 06 Dec 2005 18:19:58 -0600 [thread overview]
Message-ID: <43962AAE.4040704@serice.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0512061716030.25300@iabervon.org>
> Currently, hooks/post-update is run in the environment that
> receive-pack is run. This means that there are a number of things
> that are unpredictable. I'd like to make it set things up in a more
> predictable and useful way.
I'd like to second this. I've been bitten by two of the three issues
you've raised.
> stdout and stdin are connected to send-pack, either by broken pipes
> (for local pushes) or an ignored socket (via ssh). stdin should
> probably be /dev/null, and stdout should be either a log file or
> /dev/null. stderr is still the push's stderr, which may or may not
> be desired.
If there is a controlling terminal and nothing else git-related is
reading from it, I'd like for stdout and stderr to be reconnected.
Paul Serice
next prev parent reply other threads:[~2005-12-07 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 22:43 [RFC] Run hooks with a cleaner environment Daniel Barkalow
2005-12-07 0:19 ` Paul Serice [this message]
2005-12-07 0:39 ` Junio C Hamano
2005-12-07 17:47 ` Daniel Barkalow
2005-12-07 18:57 ` 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=43962AAE.4040704@serice.net \
--to=paul@serice.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.