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

git fetch -v not at all verbose?

From
MTMichael S. Tsirkin <mst@redhat.com>
Date
Jan 21, 2010, 16:10 UTC
Message-ID
<20100121161016.GA16300@redhat.com>
In-Reply-To
<20100121160707.GA31276@glandium.org>

Hi! On many of my trees (with linux kernel), git fetch is slower than git clone. Even more annoyingly, it would hang sometimes for tens of minutes without any output, even if -v is supplied.

stracing it shows a ton of lines like the following: 16324 read(10, "ACK 4bbdfe65d23014f539fec4227260"..., 51) = 51 16324 read(10, "0037", 4) = 4 16324 read(10, "ACK 322c06560fa314b04a6302ea03c0"..., 51) = 51 16324 read(10, "0037", 4) = 4 16324 read(10, "ACK 848ea2043b128b5947851866a114"..., 51) = 51 16324 read(10, "0037", 4) = 4

Is there some way to make got fetch show progress at this stage, or even better, can it be made faster somehow?

Thanks!
-- 
MST
Previous: Mike HommeyNext: Shawn O. Pearce
Message 14 of 28 in “problem cloning via http since v1.6.6-rc0”
  1. Yaroslav HalchenkoJan 21, 2010
  2. Tay Ray ChuanJan 21, 2010
  3. Tay Ray ChuanJan 21, 2010
  4. Yaroslav HalchenkoJan 21, 2010
  5. Tay Ray ChuanJan 21, 2010
  6. Yaroslav HalchenkoJan 21, 2010
  7. Ilari LiusvaaraJan 21, 2010
  8. Tay Ray ChuanJan 21, 2010
  9. Tay Ray ChuanJan 21, 2010
  10. Yaroslav HalchenkoJan 21, 2010
  11. http/remote-curl: coddle picky serversTay Ray Chuan, Jan 21, 2010
  12. Shawn O. PearceJan 21, 2010
  13. Mike HommeyJan 21, 2010
  14. git fetch -v not at all verbose?Michael S. Tsirkin, Jan 21, 2010
  15. Shawn O. PearceJan 21, 2010
  16. Michael S. TsirkinJan 21, 2010
  17. Shawn O. PearceJan 21, 2010
  18. Michael S. TsirkinJan 21, 2010
  19. Thomas RastJan 21, 2010
  20. Junio C HamanoJan 21, 2010
  21. Michael S. TsirkinNov 3, 2010
  22. Junio C HamanoNov 3, 2010
  23. Tay Ray ChuanJan 21, 2010
  24. Shawn O. PearceJan 21, 2010
  25. Mike HommeyJan 21, 2010
  26. Mike HommeyJan 21, 2010
  27. Ilari LiusvaaraJan 21, 2010
  28. Tay Ray ChuanJan 21, 2010

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.