From: Patrick Steinhardt <ps@pks.im>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] ci: perform build and smoke tests for Meson docs
Date: Thu, 11 Sep 2025 09:48:54 +0200 [thread overview]
Message-ID: <aMJ-5oRFtRKFnQ2s@pks.im> (raw)
In-Reply-To: <aLCf0UaTxy5Nxpv/@szeder.dev>
On Thu, Aug 28, 2025 at 08:28:33PM +0200, SZEDER Gábor wrote:
> The documentation CI job should only build the documentation, but
> these meson commands unnecessarily compile git as well:
>
> https://github.com/git/git/actions/runs/17222438141/job/48860520663#step:4:4679
>
> + meson compile -C build-asciidoc
> ninja: Entering directory `/home/runner/work/git/git/build-asciidoc'
> [1/1327] Generating hook-list.h with a custom command
> [2/1327] Generating config-list.h with a custom command
> [3/1327] Generating GIT-VERSION-FILE with a custom command (wrapped by meson to set env)
> [4/1327] Generating command-list.h with a custom command
> [5/1327] Generating version-def.h with a custom command (wrapped by meson to set env)
> [6/1327] Generating Documentation/asciidoc.conf with a custom command (wrapped by meson to set env)
> [7/1327] Generating t/clar-decls.h with a custom command
> [8/1327] Generating Documentation/cmds-ancillaryinterrogators.adoc with a custom command
> [9/1327] Generating Documentation/mergetools-diff.adoc with a custom command (wrapped by meson to set env)
> [10/1327] Compiling C object libcommon-main.a.p/common-main.c.o
> [11/1327] Compiling C object libgit.a.p/alias.c.o
> [12/1327] Compiling C object libgit.a.p/advice.c.o
> [13/1327] Compiling C object libgit.a.p/abspath.c.o
Indeed. I'll send a patch for this in a bit. Thanks!
Patrick
prev parent reply other threads:[~2025-09-11 7:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 14:28 [PATCH] ci: perform build and smoke tests for Meson docs Patrick Steinhardt
2025-08-28 18:28 ` SZEDER Gábor
2025-09-11 7:48 ` 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=aMJ-5oRFtRKFnQ2s@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=szeder.dev@gmail.com \
/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.