From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qemu: security bump to version 2.8.1.1
Date: Wed, 04 Oct 2017 11:01:28 +0200 [thread overview]
Message-ID: <87mv579thz.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20171004082217.o2yzbrwjdpicpe4r@tarshish> (Baruch Siach's message of "Wed, 4 Oct 2017 11:22:17 +0300")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
Hi,
>> -QEMU_VERSION = 2.8.0
>> +QEMU_VERSION = 2.8.1.1
>> QEMU_SOURCE = qemu-$(QEMU_VERSION).tar.bz2
> There is also a .xz tarball available.
>> QEMU_SITE = http://wiki.qemu.org/download
> This redirects to https://download.qemu.org.
Correct (for both). I wanted to keep the security bump as minimal as
possible for backport to 2017.02.x, but I can send a followup patch to
change to .xz / download.qemu.org.
Thanks for the review!
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-10-04 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 7:13 [Buildroot] [PATCH] qemu: security bump to version 2.8.1.1 Peter Korsgaard
2017-10-04 8:22 ` Baruch Siach
2017-10-04 9:01 ` Peter Korsgaard [this message]
2017-10-05 20:39 ` Peter Korsgaard
2017-10-05 20:38 ` Peter Korsgaard
2017-10-14 11:10 ` Peter Korsgaard
2017-10-17 9:04 ` 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=87mv579thz.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