Re: [PATCH] Fixup no-progress for fetch & clone

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Nicolas Pitre <nico@xxxxxxx> 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.

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]