From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Karthik Nayak <karthik.188@gmail.com>,
git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [PATCH] install meson for Documentation job
Date: Thu, 20 Mar 2025 13:27:02 -0700 [thread overview]
Message-ID: <xmqqv7s3xxbd.fsf@gitster.g> (raw)
In-Reply-To: <Z9qNNq0p10YJCZYo@pks.im> (Patrick Steinhardt's message of "Wed, 19 Mar 2025 10:24:06 +0100")
Patrick Steinhardt <ps@pks.im> writes:
> I see 4451a164e5a (install meson for Documentation job, 2025-03-14) has
> been merged, but as far as I understand we also have to take Karthik's
> patch to fix installing dependencies? In case I'm correct, do you plan
> to send this as a proper patch, Karthik?
Yes, once the Karthik's discovery is properly fixed, 4451a164
(install meson for Documentation job, 2025-03-14), which is a
misguided attempt to work around the symptom, should be discarded.
next prev parent reply other threads:[~2025-03-20 20:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 17:36 What's cooking in git.git (Mar 2025, #04; Fri, 14) Junio C Hamano
2025-03-14 18:41 ` Jeff King
2025-03-14 18:42 ` Jeff King
2025-03-15 0:02 ` Junio C Hamano
2025-03-18 15:57 ` [PATCH] install meson for Documentation job Junio C Hamano
2025-03-18 16:19 ` Karthik Nayak
2025-03-18 20:40 ` Junio C Hamano
2025-03-19 9:24 ` Patrick Steinhardt
2025-03-19 16:22 ` Karthik Nayak
2025-03-19 16:33 ` [PATCH] ci/github: add missing 'CI_JOB_IMAGE' env variable Karthik Nayak
2025-03-20 7:10 ` Patrick Steinhardt
2025-03-21 7:51 ` Junio C Hamano
2025-03-20 20:27 ` Junio C Hamano [this message]
2025-03-15 0:32 ` en/diff-rename-follow-fix (Was: Re: What's cooking in git.git (Mar 2025, #04; Fri, 14)) Elijah Newren
2025-03-15 1:22 ` en/diff-rename-follow-fix 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=xmqqv7s3xxbd.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=peff@peff.net \
--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 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).