From: Junio C Hamano <gitster@pobox•com>
To: Ramsay Jones <ramsay@ramsayjones•plus.com>
Cc: GIT Mailing-list <git@vger•kernel.org>
Subject: Re: meson build failure on 'seen'
Date: Tue, 15 Apr 2025 12:11:32 -0700 [thread overview]
Message-ID: <xmqqy0w1kzob.fsf@gitster.g> (raw)
In-Reply-To: <c358c9b7-bd83-407f-8abc-17ce9363618e@ramsayjones.plus.com> (Ramsay Jones's message of "Tue, 15 Apr 2025 18:16:02 +0100")
Ramsay Jones <ramsay@ramsayjones•plus.com> writes:
> It appears that the tip commit 916e0fb7c0 (Merge branch 'ps/meson-build-perf-bench'
> into seen, 2025-04-14) drops the call to 'find_program()' which sets/defines the
> 'target_shell' variable.
Ahh, indeed. This was the mismerge I was looking for.
Will adjust the broken merge. Thanks!
next prev parent reply other threads:[~2025-04-15 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 17:16 meson build failure on 'seen' Ramsay Jones
2025-04-15 19:11 ` Junio C Hamano [this message]
2025-04-16 8:56 ` 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=xmqqy0w1kzob.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=ramsay@ramsayjones$(echo .)plus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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