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

Bug? Unexpected outputs of git pull on stdout v.s. stderr

From
PMPascal MALAISE <malaise@magic.fr>
Date
Oct 4, 2013, 17:18 UTC
Message-ID
<524EF879.1020607@magic.fr>
Hello,

git --version -> git version 1.7.9.5 on linux

A 'git pull' operation exits with 1 (which is normal) but generates the following output and error flows:

stdout: Auto-merging c/makefile CONFLICT (content): Merge conflict in c/makefile Auto-merging c/x_color.c Auto-merging c/x_export.c CONFLICT (content): Merge conflict in c/x_export.c ... CONFLICT (content): Merge conflict in c/x_line.h Automatic merge failed; fix conflicts and then commit the result.

stderr:
From /home/malaise/ada
* branch            Xft        -> FETCH_HEAD
With option -q the Error flow is empty and the Output is as before.
I would expect that the text:
> From /home/malaise/ada
> * branch            Xft        -> FETCH_HEAD
is part of stdout and suppressed with option -q
And that the message:
> Automatic merge failed; fix conflicts and then commit the result.
is part of stderr (and kept with option -q).

Or did I miss something? Thank you.

-- 
Couldn't eradicate windows from my PC but I caged it in a vmware.
Pascal MALAISE
Message 1 of 1 in “Bug? Unexpected outputs of git pull on stdout v.s. stderr”
  1. Pascal MALAISEOct 4, 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.