From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] cmake: accommodate for `UNIT_TEST_SOURCES`
Date: Sun, 17 Aug 2025 09:12:35 -0700 [thread overview]
Message-ID: <xmqqbjoekjv0.fsf@gitster.g> (raw)
In-Reply-To: <3a5e72a3-ae92-5fa7-2bf8-4276afcfd863@gmx.de> (Johannes Schindelin's message of "Sat, 16 Aug 2025 19:09:28 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi Junio,
>
> this patch is still required; I sent this before -rc0 was released so that
> it could be included in v2.51.0 final. Could you please still merge it?
>
> Thanks,
> Johannes
Thanks for pinging. With so much traffic, a single patch without
any discussion thread went completely under the rader.
Will apply directly to 'master'.
prev parent reply other threads:[~2025-08-17 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-03 21:24 [PATCH] cmake: accommodate for `UNIT_TEST_SOURCES` Johannes Schindelin via GitGitGadget
2025-08-16 17:09 ` Johannes Schindelin
2025-08-17 16:12 ` Junio C Hamano [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqbjoekjv0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.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).