From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/21][Fido v3] pull request
Date: Mon, 08 Feb 2016 15:29:45 +0000 [thread overview]
Message-ID: <1454945385.3396.12.camel@linux.intel.com> (raw)
In-Reply-To: <cover.1454800360.git.akuster@mvista.com>
On Sat, 2016-02-06 at 15:14 -0800, Armin Kuster wrote:
> From: Armin Kuster <akuster@mvista.com>
>
> forgot to append a change to bind recipe.
>
> This includes a miss fire on the glibc request plus many others.
> This supersedes the last tow fido pull request
I've included those which weren't already present in my joshuagl/fido-
next branch.
Per Richard's request we need to document which patches are and aren't
applicable to Jethro/master and why. Can I help with that?
Regards,
Joshua
prev parent reply other threads:[~2016-02-08 15:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 23:14 [PATCH 00/21][Fido v3] pull request Armin Kuster
2016-02-06 23:14 ` [PATCH 01/21] glibc: CVE-2015-8777 Armin Kuster
2016-02-06 23:14 ` [PATCH 02/21] glibc: CVE-2015-8779 Armin Kuster
2016-02-06 23:14 ` [PATCH 03/21] glibc: CVE-2015-9761 Armin Kuster
2016-02-06 23:14 ` [PATCH 04/21] glibc: CVE-2015-8776 Armin Kuster
2016-02-06 23:14 ` [PATCH 05/21] openssl: Security fix CVE-2015-3197 Armin Kuster
2016-02-06 23:14 ` [PATCH 06/21] openssl: Security fix CVE-2016-0701 Armin Kuster
2016-02-06 23:14 ` [PATCH 07/21] subversion: fix CVE-2015-3184 Armin Kuster
2016-02-06 23:14 ` [PATCH 08/21] subversion: fix CVE-2015-3187 Armin Kuster
2016-02-06 23:14 ` [PATCH 09/21] qemu: Security fix CVE-2015-8504 Armin Kuster
2016-02-06 23:14 ` [PATCH 10/21] qemu: Security fix CVE-2015-7504 Armin Kuster
2016-02-06 23:14 ` [PATCH 11/21] qemu: Security fix CVE-2015-7512 Armin Kuster
2016-02-06 23:14 ` [PATCH 12/21] qemu: Security fix CVE-2015-8345 Armin Kuster
2016-02-06 23:14 ` [PATCH 13/21] qemu: Security fix CVE-2016-1568 Armin Kuster
2016-02-06 23:14 ` [PATCH 14/21] qemu: Security fix CVE-2015-7295 Armin Kuster
2016-02-06 23:14 ` [PATCH 15/21] tzcode: update to 2016a Armin Kuster
2016-02-06 23:14 ` [PATCH 16/21] tzdata: " Armin Kuster
2016-02-06 23:14 ` [PATCH 17/21] tzdata: reinstate changes reverted in 2014c upgrade Armin Kuster
2016-02-06 23:14 ` [PATCH 18/21] dpkg: Security fix CVE-2015-0860 Armin Kuster
2016-02-06 23:15 ` [PATCH 19/21] libxml2: Security fix CVE-2015-8241 Armin Kuster
2016-02-06 23:15 ` [PATCH 20/21] libxml2: Security fix CVE-2015-8710 Armin Kuster
2016-02-06 23:15 ` [PATCH 21/21] bind: Security fix CVE-2015-8704 Armin Kuster
2016-02-08 15:29 ` Joshua G Lock [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=1454945385.3396.12.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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