From: Junio C Hamano <junkio@cox.net>
Date: Sat, 24 Feb 2007 04:58:07 GMT
Subject: Re: [PATCH] Fixup no-progress for fetch & clone
Message-ID: <7vbqjk17a8.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <alpine.LRH.0.82.0702232141040.29426@xanadu.home>

Nicolas Pitre <nico@cam.org> writes:

> And it is not like if the whole thing was thrown away.  For example I 
> think messages like
>
> 	remote: Writing 1234 objects.
>
> are good messages to have in a log file even when progress display is 
> filtered out.  So the sideband demultiplexing is useful in that case as 
> well.

In that case, maybe we should define a separate sideband for
progress display?  Currently #1 (payload) and #3 (emergency
exit) are distinct but #2 corresponds to stderr which has info
messages and progress noise all mixed up.