From: Patrick Steinhardt <ps@pks.im>
To: phillip.wood@dunelm.org.uk
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] docs: fix check-docs with WITH_BREAKING_CHANGES
Date: Wed, 12 Mar 2025 14:43:10 +0100 [thread overview]
Message-ID: <Z9GPbggliX7asG2a@pks.im> (raw)
In-Reply-To: <75a8b321-4cf0-4d75-93a7-b616ae818d81@gmail.com>
On Wed, Mar 12, 2025 at 10:39:49AM +0000, phillip.wood123@gmail.com wrote:
> Hi Patrick
>
> On 11/03/2025 14:40, Patrick Steinhardt wrote:
> > On Mon, Mar 10, 2025 at 07:42:25AM +0100, Patrick Steinhardt wrote:
> >
> > To set expectations: do you have the time/intent to work on this and
> > polish it up into a patch? Otherwise I'm happy to pick it up.
>
> If you're happy to pick this up that would be great. I'm unlikely to have
> time for git related things for the next week or so and you're also much
> more familiar with meson than me.
Okay, I've sent the patch series in [1]. Thanks!
[1]: <20250312-b4-pks-meson-breaking-changes-v1-0-b89e9a59d228@pks.im>
Patrick
prev parent reply other threads:[~2025-03-12 13:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 16:11 [PATCH] docs: fix repository-layout when building with breaking changes Phillip Wood via GitGitGadget
2025-03-03 18:18 ` Junio C Hamano
2025-03-04 6:35 ` Patrick Steinhardt
2025-03-04 10:23 ` Phillip Wood
2025-03-04 16:04 ` Junio C Hamano
2025-03-05 10:42 ` [PATCH v2] " Phillip Wood via GitGitGadget
2025-03-05 15:53 ` [PATCH] docs: fix check-docs with WITH_BREAKING_CHANGES Junio C Hamano
2025-03-07 10:32 ` Phillip Wood
2025-03-07 15:07 ` Phillip Wood
2025-03-07 19:55 ` Junio C Hamano
2025-03-07 22:42 ` Karthik Nayak
2025-03-09 10:52 ` Phillip Wood
2025-03-09 10:52 ` Phillip Wood
2025-03-10 6:42 ` Patrick Steinhardt
2025-03-11 14:40 ` Patrick Steinhardt
2025-03-12 10:39 ` phillip.wood123
2025-03-12 13:43 ` Patrick Steinhardt [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=Z9GPbggliX7asG2a@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood@dunelm.org.uk \
/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.