Paul Smith <paul@xxxxxxxxxxxxxxxxx> writes: > I also checked and indeed, the git ls-remote command does print to both > stdout and stderr as part of its "standard" behavior: > > $ git ls-remote --heads >/dev/null > From git@git:myrepo > > This is unexpected to me, although of course there's nothing inherently > wrong with it but usually you don't expect "regular" output to go to > stderr. I suppose the idea is that people can run: > > $ git ls-remote --heads 2>/dev/null > > if they want just the output without the header. The above sounds like a reasonable expectation; then the issue is there are some fflush missing when the command writes to one stream and switches to write to another stream? Thanks.
