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

Re: [PATCHv2] connect: display connection progress

From
MTMichael S. Tsirkin <mst@dev.mellanox.co.il>
Date
May 10, 2007, 14:39 UTC
Message-ID
<20070510143913.GF22029@mellanox.co.il>
In-Reply-To
<81b0412b0705100716t680290a3qd1d10cf588a65f5a@mail.gmail.com>
Show 7 quoted lines
> >> How about cleaning up this (reduce the amount of date
> >> on screen)
> >
> >Isn't this why we have -q?
> 
> Only fetch-pack has -q (and -v, which is confusing to
> say the least).

I find it quite proper to have both. I would expect the following:

- git fetch normally displays progress meter, possibly
  tells me what stage it's in (connecting/downloading ....)
  so I know it's not hung.
- git fetch -q only tells me about errors/exceptional events
  good e.g. for scripts.
- git fetch -v gives a lot of detail useful for debugging
  only used if I see problems and want to debug.
Isn't this what's going on?
So, that's why the "connecting" message belongs in the default setup
(it can hang there for minutes), IP and such technicalia
belong with -v, and -q would only print data on connection error.
 
-- 
MST
Previous: Alex RiesenNext: Alex Riesen
Message 12 of 21 in “connect: display connection progress”
  1. connect: display connection progressMichael S. Tsirkin, May 6, 2007
  2. Junio C HamanoMay 6, 2007
  3. Michael S. TsirkinMay 7, 2007
  4. [PATCHv2] connect: display connection progressMichael S. Tsirkin, May 10, 2007
  5. Alex RiesenMay 10, 2007
  6. Michael S. TsirkinMay 10, 2007
  7. Alex RiesenMay 10, 2007
  8. Michael S. TsirkinMay 10, 2007
  9. Alex RiesenMay 10, 2007
  10. Michael S. TsirkinMay 10, 2007
  11. Alex RiesenMay 10, 2007
  12. Michael S. TsirkinMay 10, 2007
  13. Alex RiesenMay 10, 2007
  14. Michael S. TsirkinMay 10, 2007
  15. Alex RiesenMay 10, 2007
  16. Junio C HamanoMay 10, 2007
  17. Linus TorvaldsMay 10, 2007
  18. Alex RiesenMay 10, 2007
  19. Alex RiesenMay 6, 2007
  20. Michael S. TsirkinMay 7, 2007
  21. Alex RiesenMay 7, 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.