From: Junio C Hamano <gitster@pobox.com>
To: Eric Wong <e@80x24.org>
Cc: git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>
Subject: Re: batch-command wishlist [was: [TOPIC 02/12] Libification Goals and Progress]
Date: Tue, 03 Oct 2023 09:15:07 -0700 [thread overview]
Message-ID: <xmqq7co33cok.fsf@gitster.g> (raw)
In-Reply-To: <20231003005251.M353509@dcvr> (Eric Wong's message of "Tue, 3 Oct 2023 00:52:51 +0000")
Eric Wong <e@80x24.org> writes:
> Taylor Blau <me@ttaylorr.com> wrote:
>> * (Jonathan Tan) back to process isolation: is the short lifetime of the process
>> important?
>> * (Taylor Blau) seems like an impossible goal to be able to do multi-command
>> executions in a single process, the code is just not designed for it.
>
> -- Split out from https://lore.kernel.org/git/ZRrfN2lbg14IOLiK@nand.local/
> Thanks for posting in an accessible format for non-JS/video users.
>
>> * (Junio) is anybody using the `git cat-file --batch-command` mode that switches
>> between batch and batch-check.
This is not exactly what I asked about---I was asking about the use
of the "a long living process serves many requests" pattern ;-)
> But it would be nice if --batch-command grew more functionality:
>
> * ability to add/remove alternates
> * ability to specify a preferred alternate for a lookup[1]
> * detect unlinked packs/removed repos
To the third you would also want to notice an updated index, too.
> Not sure if cat-file is the place for it, but a persistent
> process to deal with:
>
> * `git config -f FILENAME ...' (especially --get-urlmatch --type=FOO)
> * approxidate parsing for other tools[2]
>
> Would also be nice...
"git daemon" ;-)?
next prev parent reply other threads:[~2023-10-03 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 0:52 batch-command wishlist [was: [TOPIC 02/12] Libification Goals and Progress] Eric Wong
2023-10-03 16:15 ` Junio C Hamano [this message]
2023-10-03 20:10 ` Jeff King
2023-10-03 20:31 ` Eric Wong
2023-10-03 20:32 ` Jeff King
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=xmqq7co33cok.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.