From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: Patrick Steinhardt <ps@pks.im>,
Phillip Wood via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [PATCH] meson: fix building technical and howto docs
Date: Mon, 03 Mar 2025 08:37:36 -0800 [thread overview]
Message-ID: <xmqqy0xmvzn3.fsf@gitster.g> (raw)
In-Reply-To: <71b5dec1-a50b-4624-87a5-b1ede8767166@gmail.com> (Phillip Wood's message of "Mon, 3 Mar 2025 14:32:57 +0000")
Phillip Wood <phillip.wood123@gmail.com> writes:
> Yes, I was hoping this minimal fix would be acceptable for inclusion
> in the upcoming release. We can change the CI once that's out the
> door.
Thanks, both. Will queue.
prev parent reply other threads:[~2025-03-03 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 16:02 [PATCH] meson: fix building technical and howto docs Phillip Wood via GitGitGadget
2025-03-03 10:17 ` Patrick Steinhardt
2025-03-03 14:32 ` Phillip Wood
2025-03-03 16:37 ` 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=xmqqy0xmvzn3.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=phillip.wood123@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--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).