git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] upload-pack: squelch progress indicator if client does not request sideband

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 16, 2009, 05:02 UTC
Message-ID
<7vprd4hito.fsf@alter.siamese.dyndns.org>
In-Reply-To
<alpine.LFD.2.00.0906152109240.16467@xanadu.home>
Nicolas Pitre <nico@cam.org> writes:
Show 13 quoted lines
>>      How did we drive upload-pack over native or ssh connection before we
>>      introduced sideband?  I vaguely recall that we relied on stderr going
>>      to the invoking terminal in the local case.  With this change, does
>>      the user suddenly stop seeing progress if the client is older than
>>      583b7ea (upload-pack/fetch-pack: support side-band communication,
>>      2006-06-21)?  If so, that would be a regression.
>
> Native, or git:// style, certainly never was able to get any kind of 
> progress display without sideband support.
>
> As to old clients using ssh... well... that could be a regression.  But 
> do we really care?  This is pre v1.4.1 after all, and even the previous 
> Debian stable was using a later git version.

I guess both ssh and local would regress, and we do care about regressions in general, but I think it is not a grave offense in this case, because the combination between such an old fetch and the updated upload-pack will still transfer the objects and will update the refs as expected; only the progress indication and chatter on the stderr stream will be lost.

So I would say it is Ok to regress in this particular case, _if_ there is no easy way to avoid it. That was why I asked:

Show 7 quoted lines
>> I think it is a very good idea to squelch progress output that will never
>> go to the client (it will be wasted traffic, regardless of the "syslog"
>> thing), but
>> 
>>  (1) Is "not using sideband" the same as "client won't see the progress
>>      output" for all vintages of clients that work with the current
>>      server?

Stated differently, I think "not using sideband _and_ spawned via daemon" would be an indication that "the client won't see the progress anyway even if it were sent." So the question becomes "will it be a small enough change to detect if the upload-pack is driven by the daemon in the codepath J6t added 'if (!use_sideband)' to, and if so shouldn't we do so?"

Previous: Nicolas PitreNext: Nicolas Pitre
Message 8 of 18 in “daemon: send stderr of service programs to the syslog”
  1. daemon: send stderr of service programs to the syslogJohannes Sixt, Jun 14, 2009
  2. Shawn O. PearceJun 15, 2009
  3. Nicolas PitreJun 15, 2009
  4. H. Peter AnvinJun 15, 2009
  5. upload-pack: squelch progress indicator if client does not request sidebandJohannes Sixt, Jun 15, 2009
  6. Junio C HamanoJun 15, 2009
  7. Nicolas PitreJun 16, 2009
  8. Junio C HamanoJun 16, 2009
  9. Nicolas PitreJun 16, 2009
  10. Johannes SixtJun 16, 2009
  11. Junio C HamanoJun 16, 2009
  12. Nicolas PitreJun 16, 2009
  13. Johannes SixtJun 15, 2009
  14. H. Peter AnvinJun 15, 2009
  15. Johannes SixtJun 16, 2009
  16. H. Peter AnvinJun 16, 2009
  17. Junio C HamanoJun 19, 2009
  18. Johannes SixtJun 20, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.