From: John Cai <johncai86@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: "Christian Couder" <christian.couder@gmail.com>,
git <git@vger.kernel.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Phillip Wood" <phillip.wood123@gmail.com>,
"Eric Wong" <e@80x24.org>
Subject: Re: [RFC v3] cat-file: add a --stdin-cmd mode
Date: Tue, 01 Feb 2022 14:27:54 -0500 [thread overview]
Message-ID: <674CD40F-7060-4892-97CD-1940AEF7C3D7@gmail.com> (raw)
In-Reply-To: <YflzZsb/txsopusP@nand.local>
Hi Taylor,
On 1 Feb 2022, at 12:52, Taylor Blau wrote:
> On Tue, Feb 01, 2022 at 10:39:30AM +0100, Christian Couder wrote:
>> Also I think at this point this should probably not be an RFC patch
>> anymore but a regular one.
>
> I think that this is due to my first "review" in [1], where I tried to
> get an understanding of what John's concrete usage plans were, since I
> couldn't figure out what they were on my own.
>
> I'm not sure that I've seen a response along the lines of "we need to
> control when the output stream is flushed in order to do ..." yet, but I
> would be interested to see one before moving too much further ahead of
> where we already are.
This would be useful when there is another process A interacting with a long
running git cat-file process B that is retrieving object information from the odb
interactively but also wants to use --buffer mode.
In this scenario, if A is asked to retrieve a large list of object metadata, it wants to
use --buffer mode to be more efficient but it would need a way to ensure that all of the
contents have been flushed to the output. If we want to keep B running to save startup time
(since otherwise we might need to spawn many git cat-file processes), then having
a flush command where we can guarantee a flush would be very handy.
>
> (Apologies if such a response was written, and I missed it).
Nope, don't think I explained the need for a flush command very clearly.
thanks
>
> Thanks,
> Taylor
>
> [1]: https://lore.kernel.org/git/YehomwNiIs0l83W7@nand.local/
next prev parent reply other threads:[~2022-02-01 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 18:33 [RFC v3] cat-file: add a --stdin-cmd mode John Cai
2022-01-31 11:44 ` Bagas Sanjaya
2022-01-31 18:24 ` Junio C Hamano
2022-02-01 9:48 ` Ævar Arnfjörð Bjarmason
2022-02-01 9:39 ` Christian Couder
2022-02-01 17:52 ` Taylor Blau
2022-02-01 19:27 ` John Cai [this message]
2022-02-01 20:14 ` Taylor Blau
[not found] ` <3FE1D509-8AD0-4F0E-9298-DFD3552A98EF@gmail.com>
2022-02-02 1:45 ` Taylor Blau
2022-02-02 13:11 ` John Cai
2022-02-01 10:43 ` Phillip Wood
2022-02-02 15:05 ` John Cai
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=674CD40F-7060-4892-97CD-1940AEF7C3D7@gmail.com \
--to=johncai86@gmail.com \
--cc=avarab@gmail.com \
--cc=christian.couder@gmail.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=phillip.wood123@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.
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 NNTP newsgroup(s).