public inbox for [email protected]
help / color / mirror / Atom feedFrom: Alvaro Herrera <[email protected]>
To: Michael Paquier <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: [email protected]
Cc: Peter Geoghegan <[email protected]>
Cc: Andrew Dunstan <[email protected]>
Cc: Jonathan S. Katz <[email protected]>
Cc: Amit Kapila <[email protected]>
Subject: Re: When to drop src/tools/msvc support
Date: Tue, 11 Apr 2023 19:44:20 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 2023-Apr-11, Michael Paquier wrote:
> Getting a CI job able to do some validation for MSVC would be indeed
> nice. What's the plan in the buildfarm with this coverage? Would all
> the animals switch to meson (Chocolatey + StrawberryPerl, I assume)
> for the job or will there still be some coverage with MSVC for v16
> there?
If we keep MSVC support in 16, then I agree we should have a CI task for
it -- and IMO we should make ti automatically triggers whenever any
Makefile or meson.build is modified. Hopefully we won't touch them
much now that the branch is feature-frozen, but it could still happen.
Do we have code for it already, even if incomplete?
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
view thread (21+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: When to drop src/tools/msvc support
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox