From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Patrick Steinhardt <ps@pks.im>,
Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org,
Kristoffer Haugsbakk <code@khaugsbakk.name>
Subject: Re: [PATCH v2] ci(win+Meson): build in Release mode
Date: Thu, 08 May 2025 11:19:49 -0700 [thread overview]
Message-ID: <xmqqmsbn55iy.fsf@gitster.g> (raw)
In-Reply-To: <3952ab1e-dc67-c47b-a86b-88b0e8886755@gmx.de> (Johannes Schindelin's message of "Tue, 6 May 2025 10:32:36 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Indeed. If we keep both bugs unfixed in `maint` (the bug that `win+Meson`
> does not build with Visual Studio, plus the bug that `win+Meson` builds in
> Debug mode), the CI will continue to pass... just not for the intended
> reasons.
That's fun ;-)
prev parent reply other threads:[~2025-05-08 18:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 15:05 [PATCH] ci(win+Meson): build in Release mode, avoiding t7001-mv hangs Johannes Schindelin via GitGitGadget
2025-04-25 15:18 ` Junio C Hamano
2025-04-28 7:47 ` Patrick Steinhardt
2025-04-28 17:01 ` Junio C Hamano
2025-04-29 12:20 ` Patrick Steinhardt
2025-04-29 20:48 ` Junio C Hamano
2025-04-30 8:58 ` Patrick Steinhardt
2025-04-30 12:46 ` Patrick Steinhardt
2025-04-29 20:57 ` Kristoffer Haugsbakk
2025-05-03 14:25 ` [PATCH v2] ci(win+Meson): build in Release mode Johannes Schindelin via GitGitGadget
2025-05-05 6:06 ` Patrick Steinhardt
2025-05-05 7:27 ` Johannes Schindelin
2025-05-05 9:43 ` Patrick Steinhardt
2025-05-05 15:54 ` Junio C Hamano
2025-05-06 7:57 ` Patrick Steinhardt
2025-05-06 8:32 ` Johannes Schindelin
2025-05-08 18:19 ` Junio C Hamano [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=xmqqmsbn55iy.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@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 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.