From: Adrian Ratiu <adrian.ratiu@collabora.com>
To: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>
Subject: Re: What's cooking in git.git (Feb 2026, #11)
Date: Mon, 02 Mar 2026 21:30:36 +0200 [thread overview]
Message-ID: <87a4wqowpv.fsf@collabora.com> (raw)
In-Reply-To: <877bru72n9.fsf@collabora.com>
On Mon, 02 Mar 2026, Adrian Ratiu <adrian.ratiu@collabora.com> wrote:
> On Fri, 27 Feb 2026, Junio C Hamano <gitster@pobox.com> wrote:
> <snip>
>> * ar/config-hooks (2026-02-18) 9 commits
>> (merged to 'next' on 2026-02-27 at 6a04cca28e)
>> + hook: add -z option to "git hook list"
>> + hook: allow out-of-repo 'git hook' invocations
>> + hook: allow event = "" to overwrite previous values
>> + hook: allow disabling config hooks
>> + hook: include hooks from the config
>> + hook: add "git hook list" command
>> + hook: run a list of hooks to prepare for multihook support
>> + hook: add internal state alloc/free callbacks
>> + Merge branch 'ar/run-command-hook-take-2' into ar/config-hooks
>> (this branch is used by ar/parallel-hooks; uses ar/run-command-hook-take-2.)
>>
>> Allow hook commands to be defined (possibly centrally) in the
>> configuration files, and run multiple of them for the same hook
>> event.
>>
>> Will merge to 'master'.
>> source: <20260218222352.55393-1-adrian.ratiu@collabora.com>
>
> Please do not merge 'ar/config-hook' (v2) yet because it still needs
> some work. Can you please remove it from next [1] ?
>
> I just sent v3 yesterday addressing all feedback from you and
> Patrick. :)
Update:
As suggested by Junio, I will rebase v3 and send it as an incremental
patch, no need to revert, since there is no actual breakage in this
series.
prev parent reply other threads:[~2026-03-02 19:30 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
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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a4wqowpv.fsf@collabora.com \
--to=adrian.ratiu@collabora.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
/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.