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

Re: stdout versus stderr for cmd line git

From
Jonathan Nieder <jrnieder@gmail.com>
Date
May 10, 2013, 03:28 UTC
Message-ID
<20130510032843.GA12036@elie>
In-Reply-To
<CAKk5qjVoDUzeurgAL51jixXsm4rJCMCDf620vAv_Gsafk8N7iA@mail.gmail.com>
Hi,
Michael Hunley wrote:
> Ok, we can filter that out.  But worse is that actual errors in a pull
> request are sent to stdout instead of standard error.  For example,
> merge conflicts or pull failures because you have unstaged changes.

Yes, errors and progress output should go to stderr. The git-pull.sh script is pretty old and is probably just a bit sloppy about forgetting to redirect output from "echo". Patches welcome. (See Documentation/SubmittingPatches for details.)

Hope that helps, Jonathan

Previous: Michael Hunley
Message 2 of 2 in “stdout versus stderr for cmd line git”
  1. Michael HunleyMay 8, 2013
  2. Jonathan NiederMay 10, 2013

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.