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

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

From
Junio C Hamano <junkio@cox.net>
Date
Feb 24, 2007, 08:14 UTC
Message-ID
<7v7iu80y6i.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<alpine.LRH.0.82.0702240005270.29426@xanadu.home>
Nicolas Pitre <nico@cam.org> writes:
> And how would the remote end distinguish how to split the info from the 
> progress noise?  Teaching pack-object about another file descriptor?
> And what happen if pack-object is run locally in that case?

That's true, and your convention to classify line with "\r" noise and others as info is as good as anything, and does not break any existing system, so it is very good one.

> How does that solve the issue with servers (currently all of them) that 
> don't know about the new sideband?
I actually happen to consider that a non problem.

It is true that you can only prepare the client and server side by 1.5.1, and new clients talking to 1.5.0 or older servers would not be able to squelch the noise. But that is _not_ a new problem anyway, and given time the server side will eventually be updated to 1.5.1 or later. If anything else, it would give incentive to people to upgrade their servers to 1.5.1 ;-)

Previous: Nicolas PitreNext: Nicolas Pitre
Message 14 of 16 in “Fixup no-progress for fetch & clone”
  1. Fixup no-progress for fetch & cloneJohannes Schindelin, Feb 23, 2007
  2. Junio C HamanoFeb 23, 2007
  3. Johannes SchindelinFeb 24, 2007
  4. Junio C HamanoFeb 24, 2007
  5. Johannes SchindelinFeb 24, 2007
  6. Nicolas PitreFeb 24, 2007
  7. Junio C HamanoFeb 24, 2007
  8. Johannes SchindelinFeb 24, 2007
  9. Nicolas PitreFeb 24, 2007
  10. Johannes SchindelinFeb 24, 2007
  11. Nicolas PitreFeb 24, 2007
  12. Junio C HamanoFeb 24, 2007
  13. Nicolas PitreFeb 24, 2007
  14. Junio C HamanoFeb 24, 2007
  15. Nicolas PitreFeb 24, 2007
  16. Jakub NarebskiFeb 24, 2007

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.