From: "Ryan, Phil." <ryanp@ewheel.de>
To: git@vger.kernel.org
Subject: git fetch --quiet inconsistently reports to STDERR
Date: Wed, 10 Dec 2014 11:46:41 +0100 [thread overview]
Message-ID: <1db81a7b475f5b2918d605082bb93e0a@elasticwheelchair.de> (raw)
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.
reply other threads:[~2014-12-10 10:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1db81a7b475f5b2918d605082bb93e0a@elasticwheelchair.de \
--to=ryanp@ewheel.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).