git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "John Cai via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: John Cai <johncai86@gmail.com>
Subject: [PATCH 0/2] cat-file: force flush of stdout on empty string
Date: Fri, 05 Nov 2021 21:56:38 +0000	[thread overview]
Message-ID: <pull.1124.git.git.1636149400.gitgitgadget@gmail.com> (raw)

When in --buffer mode, it is very useful for the caller to have control over
when the buffer is flushed. Currently there is no convenient way to signal
for the buffer to be flushed. One workaround is to provide any nonexisting
commit to git-cat-file's stdin, in which case the buffer will be flushed and
a "$FOO missing" message will be displayed. However, this is not an ideal
workaround.

Instead, this commit teaches git-cat-file to look for an empty string in
stdin, which will trigger a flush of stdout.

John Cai (2):
  cat-file: force flush of stdout on empty string
  docs: update behavior of git-cat-file --buffer

 Documentation/git-cat-file.txt |  3 ++-
 builtin/cat-file.c             | 11 ++++++++++-
 2 files changed, 12 insertions(+), 2 deletions(-)


base-commit: 6d82a21a3b699caf378cb0f89b6b0e803fc58480
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1124%2Fjohn-cai%2Fjc%2Fflush-buffer-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1124/john-cai/jc/flush-buffer-v1
Pull-Request: https://github.com/git/git/pull/1124
-- 
gitgitgadget

             reply	other threads:[~2021-11-05 21:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 21:56 John Cai via GitGitGadget [this message]
2021-11-05 21:56 ` [PATCH 1/2] cat-file: force flush of stdout on empty string John Cai via GitGitGadget
2021-11-06  0:58   ` Junio C Hamano
2021-11-06  4:01     ` Ævar Arnfjörð Bjarmason
2021-11-08  3:42       ` John Cai
2021-11-08 15:15         ` Ævar Arnfjörð Bjarmason
2021-11-08 20:11           ` Junio C Hamano
2021-11-05 21:56 ` [PATCH 2/2] docs: update behavior of git-cat-file --buffer John Cai via GitGitGadget

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pull.1124.git.git.1636149400.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johncai86@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).