From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2026, #11)
Date: Fri, 27 Mar 2026 09:08:23 -0700 [thread overview]
Message-ID: <xmqqh5q1mf0o.fsf@gitster.g> (raw)
In-Reply-To: <acYzVsWrDxzzQFGy@pks.im> (Patrick Steinhardt's message of "Fri, 27 Mar 2026 08:35:56 +0100")
Patrick Steinhardt <ps@pks.im> writes:
>> * ps/commit-graph-overflow-fix (2026-03-23) 1 commit
>> - commit-graph: fix writing generations with dates exceeding 34 bits
>> ...
>> Waiting for review response.
>> cf. <xmqq1ph92pzs.fsf@gitster.g>
>> source: <20260324-pks-commit-graph-overflow-v2-1-843568cf8780@pks.im>
>
> Hm, I think this status is probably stale, as I've sent out that
> response already
Indeed. I am not convinced by the argument "64-bit compilers would
not care if 32-bit part of the live code that it will optimize away
is not -Werror clean", but we can merge it as-is and then deal with
any fallout later, as it should be trivial to switch to conditional
compilation (the triviality is why I suggested making the change now
in the first place anyway).
>> * ar/config-hook-cleanups (2026-03-25) 13 commits
>> ...
>> Code clean-up around the recent "hooks defined in config" topic.
>>
>> Will merge to 'next'?
>> source: <20260325195503.1139418-1-adrian.ratiu@collabora.com>
>
> I'll have a look at v3 of this series series today.
Thanks.
>> * ar/parallel-hooks (2026-03-26) 13 commits
>> ...
>
> Likewise, will try to find the time to do this today.
Thanks.
next prev parent reply other threads:[~2026-03-27 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 23:16 What's cooking in git.git (Mar 2026, #11) Junio C Hamano
2026-03-27 7:35 ` Patrick Steinhardt
2026-03-27 16:08 ` Junio C Hamano [this message]
2026-03-27 8:07 ` Christian Couder
2026-03-27 16:13 ` Junio C Hamano
2026-03-31 10:37 ` Christian Couder
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=xmqqh5q1mf0o.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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.