From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH v3 1/1] libglib2: Bump to version 2.56.4
Date: Fri, 10 May 2019 11:45:03 +0200 [thread overview]
Message-ID: <878sveskww.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190316154238.864-1-petr.vorel@gmail.com> (Petr Vorel's message of "Sat, 16 Mar 2019 16:42:38 +0100")
>>>>> "Petr" == Petr Vorel <petr.vorel@gmail.com> writes:
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> ---
> Hi,
> using still 2.56.x, but I'll have a look into 2.60.x, whether it suffers the
> same problem as 2.58.x [1] [2]
According to NEWS this fixes a number of buffer overflows.
Committed to 2019.02.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-05-10 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 15:42 [Buildroot] [RFC PATCH v3 1/1] libglib2: Bump to version 2.56.4 Petr Vorel
2019-03-16 15:44 ` Petr Vorel
2019-03-17 10:29 ` Thomas Petazzoni
2019-05-10 9:45 ` Peter Korsgaard [this message]
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=878sveskww.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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