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

Re: [PATCH] git-update-index: report(...) now flushes stdout after printing the report line

From
Sebastian Thiel <byronimo@gmail.com>
Date
Dec 30, 2009, 13:56 UTC
Message-ID
<loom.20091230T145525-818@post.gmane.org>
In-Reply-To
<loom.20091119T221732-624@post.gmane.org>

I'd like to add that since version 1.6.5, non-tty's do not receive any progress information anymore. The patch causing this says it wants to, in short words, unify the push and fetch handling regarding the way progress messages are sent.

Now third-party wrappers, such as git-python, are unable to provide any progress information anymore for possibly lengthy operations.

This is why I clearly recommend to add some kind of a "progress-force" flag that turns progress messages on again for send-pack and receive-pack.

Previous: Junio C HamanoNext: Sebastian Thiel
Message 4 of 9 in “git-update-index: report(...) now flushes stdout after printing the report line”
  1. git-update-index: report(...) now flushes stdout after printing the report lineSebastian Thiel, Nov 19, 2009
  2. Nanako ShiraishiDec 30, 2009
  3. Junio C HamanoDec 30, 2009
  4. Sebastian ThielDec 30, 2009
  5. Sebastian ThielJan 3, 2010
  6. Tay Ray ChuanJan 3, 2010
  7. Sebastian ThielJan 4, 2010
  8. Junio C HamanoJan 6, 2010
  9. Tay Ray ChuanJan 6, 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.