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 (Nov 2024, #10; Thu, 28)
Date: Mon, 02 Dec 2024 09:48:35 +0900 [thread overview]
Message-ID: <xmqqmshelxjw.fsf@gitster.g> (raw)
In-Reply-To: <Z0iWMKttvtpK6f6m@pks.im> (Patrick Steinhardt's message of "Thu, 28 Nov 2024 17:11:28 +0100")
Patrick Steinhardt <ps@pks.im> writes:
>> * ps/reftable-detach (2024-11-19) 8 commits
>> ...
>> Needs review.
>> source: <cover.1731943954.git.ps@pks.im>
>
> ... it depends on this series here. From my point of view it is ready,
> as well, and has gotten a favorable review by Karthik. So I wouldn't
> mind if we merged both series to `next` together.
Indeed this has seen careful reviews. I should have updated the
status described here much earlier.
>> * ps/build (2024-11-26) 24 commits
>> ...
>> Will merge to 'next'?
>> source: <20241125-pks-meson-v9-0-1c6cf242a5f1@pks.im>
>
> I've got two small fixes pending, but other than I think the series is
> in a good enough shape for a first iteration. There's of coure a couple
> of follow-up steps that I plan to do, like wiring up CI, but I think
> it's fine to do these in a separate series.
>
> I'll send this version out in a bit. If you decide to merge, please
> note that the tip of the branch is only for compatibility with "seen"
> and should not be merged to "next".
Thanks.
next prev parent reply other threads:[~2024-12-02 0:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 5:35 What's cooking in git.git (Nov 2024, #10; Thu, 28) Junio C Hamano
2024-11-28 15:34 ` Phillip Wood
2024-12-02 0:39 ` Junio C Hamano
2024-11-28 16:11 ` Patrick Steinhardt
2024-12-02 0:48 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-28 21:40 Caleb White
2024-12-02 2:48 ` Junio C Hamano
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=xmqqmshelxjw.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.