From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] package/mariadb: bump to version 10.3.18
Date: Sun, 15 Sep 2019 22:02:46 +0200 [thread overview]
Message-ID: <20190915220246.3308ff51@windsurf.home> (raw)
In-Reply-To: <20190915193559.8464-4-bluemrp9@gmail.com>
On Sun, 15 Sep 2019 12:35:58 -0700
Ryan Coe <bluemrp9@gmail.com> wrote:
> Release notes:
> https://mariadb.com/kb/en/library/mariadb-10318-release-notes/
>
> Changelog:
> https://mariadb.com/kb/en/mariadb-10318-changelog/
>
> Signed-off-by: Ryan Coe <bluemrp9@gmail.com>
So, I assume you kept this separate from the 10.3.17 bump, because the
10.3.17 bump is a version bump that fixes security issues ?
Also, do these bumps require PATCH 1/5 ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-15 20:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 19:35 [Buildroot] [PATCH 1/5] package/mariadb: use host-openssl from buildroot-system Ryan Coe
2019-09-15 19:35 ` [Buildroot] [PATCH 2/5] package/mariadb: add bug tracker link to existing patch Ryan Coe
2019-09-30 12:18 ` Peter Korsgaard
2019-09-15 19:35 ` [Buildroot] [PATCH 3/5] package/mariadb: bump to version 10.3.17 Ryan Coe
2019-09-30 12:21 ` Peter Korsgaard
2019-09-15 19:35 ` [Buildroot] [PATCH 4/5] package/mariadb: bump to version 10.3.18 Ryan Coe
2019-09-15 20:02 ` Thomas Petazzoni [this message]
2019-09-16 13:16 ` Ryan Coe
2019-09-15 19:35 ` [Buildroot] [PATCH 5/5] package/mariadb: fix build error with newer cmake Ryan Coe
2019-09-15 20:04 ` Thomas Petazzoni
2019-09-16 13:17 ` Ryan Coe
2019-09-30 12:17 ` Peter Korsgaard
2019-09-15 20:00 ` [Buildroot] [PATCH 1/5] package/mariadb: use host-openssl from buildroot-system Thomas Petazzoni
2019-09-16 13:26 ` Ryan Coe
2019-09-21 12:51 ` Arnout Vandecappelle
2019-09-30 12:15 ` Peter Korsgaard
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=20190915220246.3308ff51@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox