From: Jeff King <peff@peff.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] fetch: don't output non-errors on stderr
Date: Sat, 26 Jun 2010 12:46:18 -0400 [thread overview]
Message-ID: <20100626164618.GA18517@coredump.intra.peff.net> (raw)
In-Reply-To: <AANLkTik6jbcOtyXJ5JJav1xnLEO6RSmYTHpsX6yYaB5_@mail.gmail.com>
On Sat, Jun 26, 2010 at 12:14:59PM +0000, Ævar Arnfjörð Bjarmason wrote:
> On Sat, Jun 26, 2010 at 06:13, Jeff King <peff@peff.net> wrote:
>
> > Or even easier: is there a reason that "git fetch -q" would not do what
> > you (Ævar) want?
>
> That'd reduce the verbosity level, which'd skip some messages that I
> might want. E.g.:
>
> if (verbosity >= 0) {
> fprintf(stderr, " x %-*s %-*s -> %s\n",
> TRANSPORT_SUMMARY_WIDTH, "[deleted]",
> REFCOL_WIDTH, "(none)", prettify_refname(ref->name));
Wait, what? Isn't that line also part of the same human-readable status
table? What makes the status of a pruned ref any different than the
status of an updated ref? I don't see how that is an error message, but
the other lines are not.
-Peff
next prev parent reply other threads:[~2010-06-26 16:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 18:06 Bugreport: Git responds with stderr instead of stdout Jack Desert
2010-04-25 18:10 ` Jacob Helwig
2010-04-25 18:24 ` Ævar Arnfjörð Bjarmason
2010-04-25 19:22 ` Jeff King
2010-04-25 19:32 ` Ævar Arnfjörð Bjarmason
2010-04-25 19:32 ` Jeff King
2010-06-12 16:52 ` Ævar Arnfjörð Bjarmason
2010-06-24 22:34 ` [PATCH] fetch: don't output non-errors on stderr Ævar Arnfjörð Bjarmason
2010-06-25 13:30 ` [PATCH v2] " Ævar Arnfjörð Bjarmason
2010-06-25 17:25 ` [PATCH] " Junio C Hamano
2010-06-25 21:28 ` Ævar Arnfjörð Bjarmason
2010-06-25 21:43 ` Junio C Hamano
2010-06-26 6:13 ` Jeff King
2010-06-26 12:14 ` Ævar Arnfjörð Bjarmason
2010-06-26 13:40 ` Tay Ray Chuan
2010-06-26 15:07 ` Ævar Arnfjörð Bjarmason
2010-06-26 16:46 ` Jeff King [this message]
2010-06-26 16:50 ` Ævar Arnfjörð Bjarmason
2010-04-25 18:34 ` Bugreport: Git responds with stderr instead of stdout Jack Desert
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=20100626164618.GA18517@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).