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

git fetch --quiet inconsistently reports to STDERR

From
RPRyan, Phil. <ryanp@ewheel.de>
Date
Dec 10, 2014, 10:46 UTC
Message-ID
<1db81a7b475f5b2918d605082bb93e0a@elasticwheelchair.de>
Hello,

I'm using git 2.0.4 and 1.7.10.4 and have discovered an issue with quiet option on fetch.

Scenario:

I am fetching from one bare repo into another bare repo and fetching from branch A to branch B. In the case that the branches have deviated from one another, --quiet surpresses all output, incl. output to STDERR.

     $ pwd
     /home/ryan_p/gitrepos/git01.git
     $ git fetch --quiet ../git02.git working_branch:master
     $ echo $?
     1
     $ git fetch ../git02.git working_branch:master
     Von ../git02
      ! [zurückgewiesen]  working_branch -> master  (kein Vorspulen)

However, if I pass a false remote name to "git fetch --quiet" I get the following:

     $ git fetch --quiet ../git02false.git working_branch:master
     fatal: '../git02false.git' does not appear to be a git repository
     fatal: Could not read from remote repository.
     Please make sure you have the correct access rights
     and the repository exists.
So, I see inconsistent behaviour here.

Further, the "git push" behaviour with the "--quiet" option corresponds to what the user actually expects:

     "-q, --quiet
            Suppress all output, including the listing of updated refs, 
unless an error occurs. Progress is not reported to the standard error 
stream."

I perceive the --quiet option on git fetch as behaving incorrectly and would like to file this as a bug.

Best Rgs,
Phil.
Message 1 of 1 in “git fetch --quiet inconsistently reports to STDERR”
  1. Ryan, Phil.Dec 10, 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.