From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: "Stefan Weil" <sw@weilnetz.de>,
"Yonggang Luo" <luoyonggang@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH for-10.1] CI: Use mingw-w64-x86_64-curl-winssl instead of mingw-w64-x86_64-curl for Windows build
Date: Wed, 6 Aug 2025 13:27:34 -0700 [thread overview]
Message-ID: <bc751ba6-db01-4278-834f-ea7b61025917@linaro.org> (raw)
In-Reply-To: <20250806200909.507803-1-sw@weilnetz.de>
On 8/6/25 1:09 PM, Stefan Weil via wrote:
> mingw-w64-x86_64-curl-winssl is required for https connections.
>
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
> ---
> .gitlab-ci.d/windows.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.gitlab-ci.d/windows.yml b/.gitlab-ci.d/windows.yml
> index 45ed0c96fe..beac39e5bd 100644
> --- a/.gitlab-ci.d/windows.yml
> +++ b/.gitlab-ci.d/windows.yml
> @@ -77,7 +77,7 @@ msys2-64bit:
> git grep make sed
> mingw-w64-x86_64-binutils
> mingw-w64-x86_64-ccache
> - mingw-w64-x86_64-curl
> + mingw-w64-x86_64-curl-winssl
> mingw-w64-x86_64-gcc
> mingw-w64-x86_64-glib2
> mingw-w64-x86_64-libnfs
Reviewed-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
next prev parent reply other threads:[~2025-08-06 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 20:09 [PATCH for-10.1] CI: Use mingw-w64-x86_64-curl-winssl instead of mingw-w64-x86_64-curl for Windows build Stefan Weil via
2025-08-06 20:27 ` Pierrick Bouvier [this message]
[not found] <c4bcc116-bd15-4c86-9e7b-3bf33b31e792@weilnetz.de>
[not found] ` <e2efea97-9cdb-4dac-bf9b-324e77a2817f@redhat.com>
2025-08-18 7:02 ` Stefan Weil via
2025-08-18 7:08 ` Thomas Huth
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=bc751ba6-db01-4278-834f-ea7b61025917@linaro.org \
--to=pierrick.bouvier@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=luoyonggang@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
--cc=thuth@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).