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

Re: [BUG] git push writes to stderr instead of stdout on success

From
Marat Radchenko <marat@slonopotamus.org>
Date
May 19, 2014, 16:43 UTC
Message-ID
<20140519164319.GA3468@seldon>
In-Reply-To
<20140519154909.GD20289@sigill.intra.peff.net>
On Mon, May 19, 2014 at 11:49:09AM -0400, Jeff King wrote:
Show 14 quoted lines
> On Mon, May 19, 2014 at 07:03:58PM +0400, Marat Radchenko wrote:
> 
> > `git push` writes to stderr instead of stdout
> 
> That's by design.
> 
> Which one is correct is largely a matter of philosophy / mental model.
> This case has been discussed before:
> 
>   http://thread.gmane.org/gmane.comp.version-control.git/180673
> 
> Keep in mind also that "git push --porcelain" does go to stdout and is
> machine-parsed, so no other messages can go to stdout when that option
> is enabled.
Oh, missed --porcelain switch. Thanks.
Previous: Jeff King
Message 3 of 3 in “[BUG] git push writes to stderr instead of stdout on success”
  1. Marat RadchenkoMay 19, 2014
  2. Jeff KingMay 19, 2014
  3. Marat RadchenkoMay 19, 2014

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.