Normally, stdout is fully buffered, unless it refers to a terminal device. This gives problems when fork() is in play: the buffer is cloned and output appears twice. By always setting stdout to line buffering, we make the output work identically for all output devices. Signed-off-by: Anders Melchiorsen <mail@xxxxxxxxxxxxxxxx> --- On #git, blix mentioned that running git clone through a pipe made it output the "Initialized empty" line twice. This seems to be due to bad interactions between fork() and buffered stdio. Rather than putting in flushing at all the right places, this sledgehammer fix simply reverts to line buffering for all output devices. Anders. git.c | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/git.c b/git.c index 37b1d76..040b900 100644 --- a/git.c +++ b/git.c @@ -421,6 +421,12 @@ int main(int argc, const char **argv) int done_alias = 0; /* + * Use line buffering, even if we do not have interactive + * output. Full buffering mixes badly with fork(). + */ + setvbuf(stdout, NULL, _IOLBF, 0); + + /* * Take the basename of argv[0] as the command * name, and the dirname as the default exec_path * if we don't have anything better. -- 1.5.6.4 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
