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
STSebastian Thiel <byronimo@googlemail.com>
Date
Jan 4, 2010, 10:30 UTC
Message-ID
<ba5802b21001040230ud27c06bw3531724862cb12c4@mail.gmail.com>
In-Reply-To
<be6fef0d1001031503h11cb65c6ha34eee345b9b7055@mail.gmail.com>

Thanks Ray Chuan, for the clarification, the progress is supposed to be sent in git-push and git-fetch ( not git-pull as I mentioned ). A --progress flag would already do it for me, is there a way to fetch your code from somewhere for a test run ?

When do you think will your changes be available for a mainline merge, or would it even be possible to separate the --progress adjustment from your feature to merge it into mainline individually ?

Thanks, Sebastian

Previous: Tay Ray ChuanNext: Junio C Hamano
Message 7 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.