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

Re: [PATCH] Provide a way to flush git-diff-tree's output

From
Junio C Hamano <junkio@cox.net>
Date
May 18, 2006, 07:24 UTC
Message-ID
<7vmzdf6bj5.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<17516.6955.282732.460675@cargo.ozlabs.ibm.com>
Paul Mackerras <paulus@samba.org> writes:
Show 7 quoted lines
> The --stdin flag to git-diff-tree is suitable for this, but the main
> difficulty is that the output of git-diff-tree gets buffered and
> doesn't get sent until the buffer is full.
>
> This provides a way to get git-diff-tree to flush its output buffers.
> If a blank line is supplied on git-diff-tree's standard input, it will
> flush its output buffers and then accept further input.
Sounds low impact and sane.

I suspect the usual caveat on bidirectional pipe deadlock applies to the caller. Does gitk do that? The current code seems to feed a pre-generated list with "open | cmd <<" construct to the command, so perhaps you are planning to change that?

Previous: Paul MackerrasNext: Paul Mackerras
Message 2 of 3 in “Provide a way to flush git-diff-tree's output”
  1. Provide a way to flush git-diff-tree's outputPaul Mackerras, May 18, 2006
  2. Junio C HamanoMay 18, 2006
  3. Paul MackerrasMay 18, 2006

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.