git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] run-command: Redirect stderr to a pipe before redirecting stdout to stderr

From
Christian Couder <chriscool@tuxfamily.org>
Date
Mar 6, 2008, 05:44 UTC
Message-ID
<20080306064415.c5ca762a.chriscool@tuxfamily.org>
In-Reply-To
<20080305083516.e1a2a139.chriscool@tuxfamily.org>
Hi Junio and Shawn,
On Wed, 5 Mar 2008, I wrote:
> With this patch, in the 'start_command' function after forking
> we now take care of stderr in the child process before stdout.
> ...
I am afraid I forgot the 
From: "Shawn O. Pearce" <spearce@spearce.org>
at the top of the patch in my last resend, so the patch was attributed to me instead of Shawn.
Is it possible to do something about it ? (I fear not since it is now in 'next' but maybe I am wrong.)

Thanks in advance, Christian.

Previous: Xavier MaillardNext: Shawn O. Pearce
Message 4 of 5 in “run-command: Redirect stderr to a pipe before redirecting stdout to stderr”
  1. run-command: Redirect stderr to a pipe before redirecting stdout to stderrChristian Couder, Mar 5, 2008
  2. Johannes SixtMar 5, 2008
  3. Xavier MaillardMar 6, 2008
  4. Christian CouderMar 6, 2008
  5. Shawn O. PearceMar 6, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.