From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Adrian Ratiu <adrian.ratiu@collabora.com>
Subject: Re: What's cooking in git.git (Feb 2026, #11)
Date: Mon, 2 Mar 2026 09:50:43 +0100 [thread overview]
Message-ID: <aaVPY9b37zY8SLup@pks.im> (raw)
In-Reply-To: <xmqq8qcdof3f.fsf@gitster.g>
On Fri, Feb 27, 2026 at 05:02:12PM -0800, Junio C Hamano wrote:
> * ar/run-command-hook-take-2 (2026-01-28) 12 commits
> (merged to 'next' on 2026-02-22 at 4aa543f115)
> + receive-pack: convert receive hooks to hook API
> + receive-pack: convert update hooks to new API
> + run-command: poll child input in addition to output
> + hook: add jobs option
> + reference-transaction: use hook API instead of run-command
> + transport: convert pre-push to hook API
> + hook: allow separate std[out|err] streams
> + hook: convert 'post-rewrite' hook in sequencer.c to hook API
> + hook: provide stdin via callback
> + run-command: add stdin callback for parallelization
> + run-command: add helper for pp child states
> + t1800: add hook output stream tests
> (this branch is used by ar/config-hooks and ar/parallel-hooks.)
>
> Use the hook API to replace ad-hoc invocation of hook scripts via
> the run_command() API.
>
> Will merge to 'master'.
> source: <20260128213927.3026875-1-adrian.ratiu@collabora.com>
It would be great if you could hold off merging this patch series for
now. There's a rather steep performance regression in the "update" hook
caused by this series, see also [1].
Thanks!
Patrick
[1]: <aaU5lZwEuR4OrxCl@pks.im>
next prev parent reply other threads:[~2026-03-02 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 1:02 What's cooking in git.git (Feb 2026, #11) Junio C Hamano
2026-03-02 8:50 ` Patrick Steinhardt [this message]
2026-03-02 19:07 ` Junio C Hamano
2026-03-02 19:20 ` Adrian Ratiu
2026-03-02 21:41 ` Junio C Hamano
2026-03-02 13:59 ` Adrian Ratiu
2026-03-02 19:30 ` Adrian Ratiu
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=aaVPY9b37zY8SLup@pks.im \
--to=ps@pks.im \
--cc=adrian.ratiu@collabora.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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