From: Junio C Hamano <gitster@pobox.com>
To: Adrian Ratiu <adrian.ratiu@collabora.com>
Cc: git@vger.kernel.org, Emily Shaffer <emilyshaffer@google.com>,
Rodrigo Damazio Bovendorp <rdamazio@google.com>,
Junio C Hamano <gitster@pobox.com>,
Patrick Steinhardt <ps@pks.im>,
Josh Steadmon <steadmon@google.com>,
Ben Knoble <ben.knoble@gmail.com>,
Phillip Wood <phillip.wood123@gmail.com>,
Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
Adrian Ratiu <adrian.ratiu@collabora.com>
Subject: Re: What's cooking in git.git (Dec 2025, #03)
Date: Tue, 16 Dec 2025 10:59:56 +0900 [thread overview]
Message-ID: <xmqq1pkv5gpv.fsf@gitster.g> (raw)
In-Reply-To: <87ldj6x1ys.fsf@gentoo.mail-host-address-is-not-set> (Adrian Ratiu's message of "Sat, 13 Dec 2025 09:42:03 +0200")
Adrian Ratiu <adrian.ratiu@collabora.com> writes:
> On Fri, 12 Dec 2025, Junio C Hamano <gitster@pobox.com> wrote:
>> * ar/run-command-hook (2025-12-04) 11 commits
>> ...
>> Use hook API to replace ad-hoc invocation of hook scripts with the
>> run_command() API.
>>
>> Will merge to 'next'?
>> source: <20251204141535.1986263-1-adrian.ratiu@collabora.com>
>
> I think this can be merged to next, since the latest iteration has been
> sitting for a few weeks with no more feedback and all tests are green.
"tests being green" tells us that with the current coverage we
didn't see any regression but not more than that. Especially, it
does not say anything about the quality of new code (and test) and
if it is in good shape to build on top.
It also is very hard to tell from "no more feedback" if there is no
room for further improvements, or people are simply disinterested in
the topic and are not tempted to spend their brain cycles to help
improve the topic.
If there is no more comments, I'll try to see if I can block some
time to read the topic over myself with a pair of fresh eyes before
deciding.
Thanks for pinging.
next prev parent reply other threads:[~2025-12-16 1:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 10:26 What's cooking in git.git (Dec 2025, #03) Junio C Hamano
2025-12-13 7:42 ` Adrian Ratiu
2025-12-16 1:59 ` Junio C Hamano [this message]
2025-12-16 8:13 ` Patrick Steinhardt
2025-12-16 10:41 ` Adrian Ratiu
2025-12-16 17:49 ` Emily Shaffer
2025-12-17 5:04 ` Junio C Hamano
2025-12-13 18:45 ` René Scharfe
2025-12-17 0:09 ` Aaron Plattner
2025-12-17 5:02 ` Junio C Hamano
2025-12-17 5:20 ` Aaron Plattner
2025-12-17 6:18 ` Jeff King
2025-12-17 13:46 ` Junio C Hamano
2025-12-17 20:26 ` Aaron Plattner
2025-12-18 2:57 ` Junio C Hamano
2025-12-18 6:22 ` Patrick Steinhardt
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=xmqq1pkv5gpv.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=adrian.ratiu@collabora.com \
--cc=ben.knoble@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=phillip.wood123@gmail.com \
--cc=ps@pks.im \
--cc=rdamazio@google.com \
--cc=steadmon@google.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;
as well as URLs for NNTP newsgroup(s).