From: Toon Claes <toon@iotcl•com>
To: git@vger•kernel.org
Cc: Patrick Steinhardt <ps@pks•im>, Toon Claes <toon@iotcl•com>
Subject: [PATCH v2 0/2] Harden test t0450-txt-doc-vs-help
Date: Fri, 8 Aug 2025 11:59:41 +0200 [thread overview]
Message-ID: <20250808095943.3312265-1-toon@iotcl.com> (raw)
In-Reply-To: <20250804073002.1586332-1-toon@iotcl.com>
These patches add a few improvements to test t0450-txt-doc-vs-help.
When using Meson, some test cases seem to have been skipped. This
happened because it was looking for .adoc files in the wrong location.
The first patch fixes that issue.
But, because these tests were skipped silently (when using Meson), I did
not notice breakage in another patch series of mine. To harden the test,
the second patch adds an allowlist.
Toon Claes (2):
t0450: fix test for out-of-tree builds
t0450: add allowlist for builtins with missing .adoc
t/t0450-txt-doc-vs-help.sh | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
Range-diff against v1:
1: 184290765e = 1: cc1dd21b1c t0450: fix test for out-of-tree builds
-: ---------- > 2: b8c6d88c47 t0450: add allowlist for builtins with missing .adoc
base-commit: 2c2ba49d55ff26c1082b8137b1ec5eeccb4337d1
prerequisite-patch-id: 0000000000000000000000000000000000000000
--
2.50.1.327.g047016eb4a
next prev parent reply other threads:[~2025-08-08 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 7:30 [PATCH] t0450: fix test for out-of-tree builds Toon Claes
2025-08-04 7:56 ` Patrick Steinhardt
2025-08-05 12:11 ` Toon Claes
2025-08-08 9:59 ` Toon Claes [this message]
2025-08-08 9:59 ` [PATCH v2 1/2] " Toon Claes
2025-08-08 9:59 ` [PATCH v2 2/2] t0450: add allowlist for builtins with missing .adoc Toon Claes
2025-08-08 22:07 ` Junio C Hamano
2025-08-12 12:52 ` Patrick Steinhardt
2025-08-28 23:12 ` Junio C Hamano
2025-09-02 20:57 ` Junio C Hamano
2025-09-03 11:26 ` Toon Claes
2025-09-03 18:46 ` 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=20250808095943.3312265-1-toon@iotcl.com \
--to=toon@iotcl$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=ps@pks$(echo .)im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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