From: "Laszlo Ersek" <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Wang, Jian J" <jian.j.wang@intel.com>,
"Wu, Hao A" <hao.a.wu@intel.com>,
Cinnamon Shia <cinnamon.shia@hpe.com>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"afish@apple.com" <afish@apple.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Cetola, Stephano" <stephano.cetola@intel.com>
Subject: Re: [edk2-devel] [Patch] MdeModulePkg RegularExpressionDxe: Update Oniguruma from v6.9.0 to v6.9.3
Date: Thu, 8 Aug 2019 22:34:16 +0200 [thread overview]
Message-ID: <30cc2689-ec3b-8f31-541a-221bf6e6167b@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E4CCE86@SHSMSX104.ccr.corp.intel.com>
On 08/08/19 15:52, Gao, Liming wrote:
> Hi, all
> This patch is big. I upload it into https://github.com/lgao4/edk2/tree/Oniguruma6.9.3 for your review.
>
> Hi, Stewards:
> Oniguruma version v6.9.3 is released for security fix. So, I plan to include this update for 201908 stable tag. If you have any comments, please let me know.
I would generally prefer large updates near the beginning of the
development cycle, but I can see that
<https://github.com/kkos/oniguruma/releases/tag/v6.9.3> was released
just three days ago. So, no objection from me.
I have a separate suggestion: can you please file a TianoCore feature
request BZ for the next development cycle, for investigating whether we
can consume Oniguruma through a git submodule?
Thanks,
Laszlo
next prev parent reply other threads:[~2019-08-08 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15B8F5E6C2C74026.10163@groups.io>
2019-08-08 13:52 ` [edk2-devel] [Patch] MdeModulePkg RegularExpressionDxe: Update Oniguruma from v6.9.0 to v6.9.3 Liming Gao
2019-08-08 14:51 ` Leif Lindholm
2019-08-09 13:51 ` Liming Gao
2019-08-08 20:34 ` Laszlo Ersek [this message]
2019-08-12 5:07 ` Wu, Hao A
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-list 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=30cc2689-ec3b-8f31-541a-221bf6e6167b@redhat.com \
--to=devel@edk2.groups.io \
/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