From: Karthik Nayak <karthik.188@gmail.com>
To: Patrick Steinhardt <ps@pks.im>, git@vger.kernel.org
Cc: Phillip Wood <phillip.wood123@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 0/3] meson: improve handling of `-Dbreaking_changes=true`
Date: Thu, 13 Mar 2025 04:08:25 -0700 [thread overview]
Message-ID: <CAOLa=ZR6Y1rE7BmJ-gUov_b9DNPs1q7ZDz0v0uUShkN6vVtDjw@mail.gmail.com> (raw)
In-Reply-To: <20250312-b4-pks-meson-breaking-changes-v1-0-b89e9a59d228@pks.im>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
Patrick Steinhardt <ps@pks.im> writes:
> Hi,
>
> this small patch series improves handling of the breaking changes option
> with the Meson build system as discussed in the thread starting at [1].
>
> Thanks!
>
> Patrick
>
> [1]: <56cf842a-7c1f-4354-b191-35bcc1e139bd@gmail.com>
>
Thanks for picking this up. I think the series looks good, and is inline
with the discussion we had earlier.
> ---
> Patrick Steinhardt (3):
> meson: define WITH_BREAKING_CHANGES when enabling breaking changes
> meson: don't compile git-pack-redundant(1) with breaking changes
> meson: don't install git-pack-redundant(1) docs with breaking changes
>
> Documentation/Makefile | 2 +-
> Documentation/meson.build | 13 +++++++++++--
> meson.build | 18 +++++++++++-------
> 3 files changed, 23 insertions(+), 10 deletions(-)
>
>
> ---
> base-commit: 87a0bdbf0f72b7561f3cd50636eee33dcb7dbcc3
> change-id: 20250312-b4-pks-meson-breaking-changes-819afcca2e07
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 690 bytes --]
prev parent reply other threads:[~2025-03-13 11:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 13:17 [PATCH 0/3] meson: improve handling of `-Dbreaking_changes=true` Patrick Steinhardt
2025-03-12 13:17 ` [PATCH 1/3] meson: define WITH_BREAKING_CHANGES when enabling breaking changes Patrick Steinhardt
2025-03-12 13:17 ` [PATCH 2/3] meson: don't compile git-pack-redundant(1) with " Patrick Steinhardt
2025-03-12 13:17 ` [PATCH 3/3] meson: don't install git-pack-redundant(1) docs " Patrick Steinhardt
2025-03-13 11:07 ` Karthik Nayak
2025-03-16 15:19 ` Phillip Wood
2025-03-17 13:57 ` Patrick Steinhardt
2025-03-17 14:50 ` Phillip Wood
2025-03-18 10:06 ` Phillip Wood
2025-03-19 9:37 ` Patrick Steinhardt
2025-03-13 11:08 ` Karthik Nayak [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='CAOLa=ZR6Y1rE7BmJ-gUov_b9DNPs1q7ZDz0v0uUShkN6vVtDjw@mail.gmail.com' \
--to=karthik.188@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood123@gmail.com \
--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).