From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Sat, 26 Jun 2010 15:07:55 GMT
Subject: Re: [PATCH] fetch: don't output non-errors on stderr
Message-ID: <AANLkTikxJ_MDLhQFweRMWvhzJy9QIfyuJTYaY4a2tPwS@mail.gmail.com>
In-Reply-To: <AANLkTikq4z5Qs6UUnSh8T9GjVTJBdH8Wy3djIIOlrs2Y@mail.gmail.com>

On Sat, Jun 26, 2010 at 13:40, Tay Ray Chuan <rctay89@gmail.com> wrote:

> On Sat, Jun 26, 2010 at 8:14 PM, Ævar Arnfjörð Bjarmason
> <avarab@gmail.com> wrote:
>> But it sounds like we need some general discussion on what stdout and
>> stderr should be used for in Git with regards to progress messages,
>> errors and other similar things.
>
> I'd say - submit a patch for the style guide with your proposed
> guidelines on stdout and stderr usage.

I'm not sure how such a guide should be like for the general case, but
at least making commands internally consistent (as this patch does) is
one step in that direction.