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>, John Cai <johncai86@gmail.com>
Subject: [PATCH 2/2] docs: update behavior of git-cat-file --buffer
Date: Fri, 05 Nov 2021 21:56:40 +0000	[thread overview]
Message-ID: <18d6c2819ade2e514a408e4173c6a5048e3f2cd1.1636149400.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1124.git.git.1636149400.gitgitgadget@gmail.com>

From: John Cai <johncai86@gmail.com>

When an empty string is entered into stdin, git-cat-file --buffer will
flush stdout immediately. This commit updates the man page accordingly.

Signed-off-by: John Cai <johncai86@gmail.com>
---
 Documentation/git-cat-file.txt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Documentation/git-cat-file.txt b/Documentation/git-cat-file.txt
index 27b27e2b300..c98e8dc3669 100644
--- a/Documentation/git-cat-file.txt
+++ b/Documentation/git-cat-file.txt
@@ -104,7 +104,8 @@ OPTIONS
 	that a process can interactively read and write from
 	`cat-file`. With this option, the output uses normal stdio
 	buffering; this is much more efficient when invoking
-	`--batch-check` on a large number of objects.
+	`--batch-check` on a large number of objects. An empty string will
+	force a flush of stdout.
 
 --unordered::
 	When `--batch-all-objects` is in use, visit objects in an
-- 
gitgitgadget

      parent 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 [PATCH 0/2] cat-file: force flush of stdout on empty string John Cai via GitGitGadget
2021-11-05 21:56 ` [PATCH 1/2] " 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 ` John Cai via GitGitGadget [this message]

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=18d6c2819ade2e514a408e4173c6a5048e3f2cd1.1636149400.git.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).