From: Phillip Wood <phillip.wood123@gmail.com>
To: Patrick Steinhardt <ps@pks.im>, git@vger.kernel.org
Cc: Karthik Nayak <karthik.188@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 3/3] meson: don't install git-pack-redundant(1) docs with breaking changes
Date: Sun, 16 Mar 2025 15:19:48 +0000 [thread overview]
Message-ID: <44a3ad4e-fb50-447f-bb66-f43b5c5ae012@gmail.com> (raw)
In-Reply-To: <20250312-b4-pks-meson-breaking-changes-v1-3-b89e9a59d228@pks.im>
Hi Patrick
On 12/03/2025 13:17, Patrick Steinhardt wrote:
Thanks for taking this forward
> +manpages_breaking_changes = {
> + 'git-pack-redundant.adoc' : 1,
> +}
> +
> +if not get_option('breaking_changes')
> + manpages += manpages_breaking_changes
> +endif
> +
> docs_backend = get_option('docs_backend')
> if docs_backend == 'auto'
> if find_program('asciidoc', dirs: program_path, required: false).found()
> @@ -479,7 +486,9 @@ endif
> # Sanity check that we are not missing any tests present in 't/'. This check
> # only runs once at configure time and is thus best-effort, only. Furthermore,
> # it only verifies man pages for the sake of simplicity.
> -configured_manpages = manpages.keys() + [ 'git-bisect-lk2009.adoc', 'git-tools.adoc' ]
> +configured_manpages = manpages.keys()
> +configured_manpages += manpages_breaking_changes.keys()
> +configured_manpages += [ 'git-bisect-lk2009.adoc', 'git-tools.adoc' ]
I don't think we need this hunk as we add manpages_breaking_changes into
manpages in the hunk above.
Best Wishes
Phillip
next prev parent reply other threads:[~2025-03-16 15:19 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 [this message]
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 ` [PATCH 0/3] meson: improve handling of `-Dbreaking_changes=true` Karthik Nayak
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=44a3ad4e-fb50-447f-bb66-f43b5c5ae012@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=karthik.188@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).