From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Jie Zhou <jizh@linux.microsoft.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"roretzla@linux.microsoft.com" <roretzla@linux.microsoft.com>,
Jie Zhou <jizh@microsoft.com>,
Narcisa Vasile <navasile@linux.microsoft.com>,
dmitrym@microsoft.com, pallavi.kadam@intel.com,
bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [EXTERNAL] [PATCH] WindowsGSGDoc: Update the meson version to use for Windows DPDK
Date: Wed, 17 Mar 2021 03:00:47 +0300 [thread overview]
Message-ID: <20210317030047.4a102cfc@sovereign> (raw)
In-Reply-To: <7214899.8EVLAoSQA2@thomas>
2021-03-16 12:09 (UTC+0100), Thomas Monjalon:
> 08/03/2021 19:32, Jie Zhou:
[...]
> > -Recommended version is either Meson 0.47.1 (baseline) or the latest release.
> > +Recommended version is either Meson 0.57.0 (baseline) or the latest release.
>
> I am OK with the change. What others think?
Although I can't reproduce it with meson 0.53.2 and 0.56.2 and I wonder why it
doesn't affect examples as well, the issue exists in meson tracker:
https://github.com/mesonbuild/meson/issues/8060
On Windows, there's no repository to constrain meson version from above,
so if 0.57.0 has no known issues, let's recommend it.
Acked-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
next prev parent reply other threads:[~2021-03-17 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 23:36 [dpdk-dev] [PATCH] WindowsGSGDoc: Update the meson version to use for Windows DPDK Jie Zhou
2021-03-08 18:32 ` [dpdk-dev] [EXTERNAL] " Jie Zhou
2021-03-16 11:09 ` Thomas Monjalon
2021-03-17 0:00 ` Dmitry Kozlyuk [this message]
2021-04-16 17:51 ` Thomas Monjalon
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=20210317030047.4a102cfc@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dmitrym@microsoft.com \
--cc=jizh@linux.microsoft.com \
--cc=jizh@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=roretzla@linux.microsoft.com \
--cc=thomas@monjalon.net \
/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.