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

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

 



On Sat, 24 Feb 2007, Johannes Schindelin wrote:

> Hi,
> 
> On Fri, 23 Feb 2007, Nicolas Pitre wrote:
> 
> > And I would do that and _only_ that to supress progress.  No messing 
> > around with protocol extensions.  Just filter out the unwanted messages 
> > locally and be happy.
> 
> This is easier, but I'd feel dirty about it. I mean, you set up a signal 
> every so often, have a side band, demultiplex the side band, and for what? 
> To just ignore it?

Yes sir.  But of course this isn't the default.  

And it isn't even the common case either.  So I think a bit of cheating 
to keep the common case simple isn't that bad.

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.


Nicolas
-
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]