git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	git@vger.kernel.org, nanako3@bluebottle.com, pascal@obry.net,
	Xavier Maillard <xma@gnu.org>
Subject: Re: [PATCH] run-command: Redirect stderr to a pipe before redirecting stdout to stderr
Date: Wed, 05 Mar 2008 08:36:19 +0100	[thread overview]
Message-ID: <47CE4D73.4050607@viscovery.net> (raw)
In-Reply-To: <20080305083516.e1a2a139.chriscool@tuxfamily.org>

Christian Couder schrieb:
> With this patch, in the 'start_command' function after forking
> we now take care of stderr in the child process before stdout.
> 
> This way if 'start_command' is called with a 'child_process'
> argument like this:
> 
> 	.err = -1;
> 	.stdout_to_stderr = 1;
> 
> then stderr will be redirected to a pipe before stdout is
> redirected to stderr. So we can now get the process' stdout
> from the pipe (as well as its stderr).
> 
> Earlier such a call would have redirected stdout to stderr
> before stderr was itself redirected, and therefore stdout
> would not have followed stderr, which would not have been
> very useful anyway.
> 
> Update documentation in 'api-run-command.txt' accordingly.
> 
> Signed-off-by: Christian Couder <chriscool@tuxfamily.org>

FWIW:

Acked-by: Johannes Sixt <johannes.sixt@telecom.at>

-- Hannes


  reply	other threads:[~2008-03-05  7:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05  7:35 [PATCH] run-command: Redirect stderr to a pipe before redirecting stdout to stderr Christian Couder
2008-03-05  7:36 ` Johannes Sixt [this message]
2008-03-06  1:00 ` Xavier Maillard
2008-03-06  5:44 ` Christian Couder
2008-03-06  6:42   ` Shawn O. Pearce
  -- strict thread matches above, loose matches on Subject: below --
2008-03-03 19:06 Christian Couder

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=47CE4D73.4050607@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nanako3@bluebottle.com \
    --cc=pascal@obry.net \
    --cc=spearce@spearce.org \
    --cc=xma@gnu.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).