From: Ryan, Phil. <ryanp@ewheel.de>
Date: Wed, 10 Dec 2014 10:46:41 GMT
Subject: git fetch --quiet inconsistently reports to STDERR
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.