From: Max Reitz <mreitz@redhat.com>
To: Yonggang Luo <luoyonggang@gmail.com>, qemu-devel@nongnu.org
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Kevin Wolf <kwolf@redhat.com>, Peter Lieven <pl@kamp.de>,
qemu-block@nongnu.org
Subject: Re: [PATCH v2 2/2] block: enable libnfs on msys2/mingw in cirrus.yml
Date: Thu, 5 Nov 2020 12:43:20 +0100 [thread overview]
Message-ID: <2e501256-001e-a9c4-305c-f178d1b53137@redhat.com> (raw)
In-Reply-To: <20201013001545.1958-3-luoyonggang@gmail.com>
On 13.10.20 02:15, Yonggang Luo wrote:
> At the begging libnfs are not enabled because of compiling error,
> now it's fixed so enable it
>
> Signed-off-by: Yonggang Luo <luoyonggang@gmail.com>
> ---
> .cirrus.yml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/.cirrus.yml b/.cirrus.yml
> index f42ccb956a..2c6bf45e6d 100644
> --- a/.cirrus.yml
> +++ b/.cirrus.yml
> @@ -109,6 +109,7 @@ windows_msys2_task:
> mingw-w64-x86_64-cyrus-sasl \
> mingw-w64-x86_64-curl \
> mingw-w64-x86_64-gnutls \
> + mingw-w64-x86_64-libnfs \
> "
> bitsadmin /transfer msys_download /dynamic /download /priority FOREGROUND `
> https://repo.msys2.org/mingw/x86_64/mingw-w64-x86_64-python-sphinx-2.3.1-1-any.pkg.tar.xz `
I’d love to test this, unfortunately git.qemu.org has some issues now
and so I can’t run Cirrus tests. :/
I suppose I’ll retry when git.qemu.org works again.
Max
next prev parent reply other threads:[~2020-11-05 11:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 0:15 [PATCH v2 0/2] Fixes building nfs on msys2/mingw Yonggang Luo
2020-10-13 0:15 ` [PATCH v2 1/2] block: Fixes nfs compiling error " Yonggang Luo
2020-11-05 11:29 ` Max Reitz
2020-11-05 11:32 ` 罗勇刚(Yonggang Luo)
2020-11-05 11:43 ` Max Reitz
2020-11-05 11:46 ` 罗勇刚(Yonggang Luo)
2020-11-05 12:11 ` Max Reitz
2020-11-05 12:32 ` 罗勇刚(Yonggang Luo)
2020-10-13 0:15 ` [PATCH v2 2/2] block: enable libnfs on msys2/mingw in cirrus.yml Yonggang Luo
2020-11-05 11:43 ` Max Reitz [this message]
2020-11-05 12:32 ` 罗勇刚(Yonggang Luo)
2020-11-05 14:40 ` Max Reitz
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=2e501256-001e-a9c4-305c-f178d1b53137@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=luoyonggang@gmail.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/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).