From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: ab/hooks-regression-fix (was: What's cooking in git.git (Jun 2022, #01; Wed, 1))
Date: Thu, 02 Jun 2022 16:47:55 +0200 [thread overview]
Message-ID: <220602.86wndzxgsl.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqee07q3xc.fsf@gitster.g>
On Wed, Jun 01 2022, Junio C Hamano wrote:
> * ab/hooks-regression-fix (2022-06-01) 2 commits
> - hook API: fix v2.36.0 regression: hooks should be connected to a TTY
> - run-command: add an "ungroup" option to run_process_parallel()
>
> In Git 2.36 we revamped the way how hooks are invoked. One change
> that is end-user visible is that the output of a hook is no longer
> directly connected to the standard output of "git" that spawns the
> hook, which was noticed post release. This is getting corrected.
>
> Under discussion.
> source: <cover-v4-0.2-00000000000-20220531T173005Z-avarab@gmail.com>
Re-rolled
https://lore.kernel.org/git/cover-v5-0.2-00000000000-20220602T131858Z-avarab@gmail.com/
which (hopefully) addresses the outstanding comments, allowing this to
move forward.
prev parent reply other threads:[~2022-06-02 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 0:55 What's cooking in git.git (Jun 2022, #01; Wed, 1) Junio C Hamano
2022-06-02 1:16 ` gc/zero-length-branch-config-fix (was Re: What's cooking in git.git (Jun 2022, #01; Wed, 1)) Glen Choo
2022-06-02 8:37 ` Ævar Arnfjörð Bjarmason
2022-06-02 12:13 ` ab/env-array (was: " Ævar Arnfjörð Bjarmason
2022-06-02 12:25 ` What's cooking in git.git (Jun 2022, #01; Wed, 1) Derrick Stolee
2022-06-02 14:07 ` Jeff Hostetler
2022-06-02 14:46 ` ab/bug-if-bug (was: What's cooking in git.git (Jun 2022, #01; Wed, 1)) Ævar Arnfjörð Bjarmason
2022-06-02 14:47 ` Ævar Arnfjörð Bjarmason [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=220602.86wndzxgsl.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).