public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
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 15:59:54 +0200	[thread overview]
Message-ID: <877bru72n9.fsf@collabora.com> (raw)
In-Reply-To: <xmqq8qcdof3f.fsf@gitster.g>

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. :)

This might be orthogonal to the update regression Patrick reported, I
will look into that separately.

Many thanks,
Adrian

1:
commit 6a04cca28e210f0c51cfefcb52475c7ede6e99fb
Merge: d6ebc97cb1 4b12cd3ae3
Author:     Junio C Hamano <gitster@pobox.com>
AuthorDate: Fri Feb 27 15:16:30 2026 -0800
Commit:     Junio C Hamano <gitster@pobox.com>
CommitDate: Fri Feb 27 15:16:30 2026 -0800

    Merge branch 'ar/config-hooks' into next
    
    Allow hook commands to be defined (possibly centrally) in the
    configuration files, and run multiple of them for the same hook
    event.
    
    * ar/config-hooks:
      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

  parent reply	other threads:[~2026-03-02 14:00 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 [this message]
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=877bru72n9.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox