Re: [PATCH] fetch: don't output non-errors on stderr

From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Jun 26, 2010, 16:50 UTC
Message-ID: <AANLkTinOHlHgb1GrHPZrC8Rs0l4XNNf8lqRvhRaWPVPz@mail.gmail.com>
In-Reply-To: <20100626164618.GA18517@coredump.intra.peff.net>

On Sat, Jun 26, 2010 at 16:46, Jeff King <peff@peff.net> wrote:

Show 19 quoted lines

> 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.

I misread that and picked the wrong example, sorry for the noise.