Git development
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Patrick Steinhardt <ps@pks.im>, git@vger.kernel.org
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 0/7] A couple of Meson improvements
Date: Mon, 5 Oct 2026 15:21:16 +0530	[thread overview]
Message-ID: <24737aed-50c5-4536-a081-938036c08588@gmail.com> (raw)
In-Reply-To: <20260924-pks-meson-improvements-v1-0-90b7f79f1c4e@pks.im>

On 9/24/26 19:39, Patrick Steinhardt wrote:
>
> ---
> Patrick Steinhardt (7):
>        meson: avoid recompiling HTTP sources several times
>        meson: don't recompile git-remote-http(1) multiple times for tests
>        meson: use precompiled headers for our test-helper
>        meson: use precompiled headers for unit tests

The only other sub-directory that does not yet include the precompiled 
header is 'compat' and leaving it out seems to be the right choice. 
Including it would trigger recursive compilation issues as 
git-compat-util.h itself depends on compat/posix.h. Trying to reshuffle 
the build code to fix this seems not worthwhile given the amount of code 
is a bit less there.

A few other similar targets that were not touched by this series are 
non-worthwhile such as 'common-main', 'git-curl' etc.

Apart from the few other comments in other threads, this series looks 
good to me.

-- 
Sivaraam


      parent reply	other threads:[~2026-10-05  9:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 14:09 [PATCH 0/7] A couple of Meson improvements Patrick Steinhardt
2026-09-24 14:09 ` [PATCH 1/7] meson: avoid recompiling HTTP sources several times Patrick Steinhardt
2026-09-30 12:00   ` Karthik Nayak
2026-10-05  8:03   ` Kaartic Sivaraam
2026-09-24 14:09 ` [PATCH 2/7] meson: don't recompile git-remote-http(1) multiple times for tests Patrick Steinhardt
2026-09-24 14:09 ` [PATCH 3/7] meson: use precompiled headers for our test-helper Patrick Steinhardt
2026-09-30 12:20   ` Karthik Nayak
2026-09-24 14:09 ` [PATCH 4/7] meson: use precompiled headers for unit tests Patrick Steinhardt
2026-10-05  9:34   ` Kaartic Sivaraam
2026-10-05 10:24     ` Patrick Steinhardt
2026-09-24 14:09 ` [PATCH 5/7] meson: fix outdated completion helpers Patrick Steinhardt
2026-09-24 14:09 ` [PATCH 6/7] meson: update wrappers Patrick Steinhardt
2026-09-30 12:24   ` Karthik Nayak
2026-10-05  9:42   ` Kaartic Sivaraam
2026-10-05 10:25     ` Patrick Steinhardt
2026-09-24 14:09 ` [PATCH 7/7] gitlab-ci: fix hanging MSVC jobs Patrick Steinhardt
2026-09-30 12:26   ` Karthik Nayak
2026-09-30 12:48     ` Patrick Steinhardt
2026-09-30 12:26 ` [PATCH 0/7] A couple of Meson improvements Karthik Nayak
2026-10-05  9:51 ` Kaartic Sivaraam [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=24737aed-50c5-4536-a081-938036c08588@gmail.com \
    --to=kaartic.sivaraam@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --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