From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>, akuster808 <akuster808@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 00/20] Dizzy-next pull request 2016-1
Date: Sat, 30 Jan 2016 12:06:29 +0000 [thread overview]
Message-ID: <1454155589.27087.3.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+chaQcaWoZE_Cru1YZGd+AahFx7y_jBapZFG9rxuKcJrE=aXg@mail.gmail.com>
On Sat, 2016-01-30 at 10:08 +0100, Martin Jansa wrote:
> > that was a patch from the patch queue and affect glibc below 2.21
> so
>
> glibc/wscanf: CVE-2015-1472
>
> looks like better subject
>
> > Dizzy 1.7.4 is not planned yet.
>
> I don't care about point releases, I care only about contents of
> release branch, can it be merged to dizzy branch?
I was hoping the branch would get corrected so I could then just pull
the correct commits. I suspect Armin didn't realise I was waiting for
that.
In the interests of expedience, I've reworded that commit and merged
the branch.
There are a couple of tweaks that would make things easier for me to
take these:
a) Could you in the 00/XX series header in future confirm you've
checked and that these issues are addressed in the later stable
branches? I do worry that for example there may be unaddressed issues
in fido.
b) If you could share an oe-core contrib branch with these in, it does
make it easier for me to merge them. I can deal with that comparatively
easily though.
I have merged this to dizzy though.
Cheers,
Richard
next prev parent reply other threads:[~2016-01-30 12:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 0:30 [PATCH 00/20] Dizzy-next pull request 2016-1 Armin Kuster
2016-01-10 0:30 ` [PATCH 01/20] libtasn1: CVE-2015-3622 Armin Kuster
2016-01-10 0:30 ` [PATCH 02/20] grep2.19: CVE-2015-1345 Armin Kuster
2016-01-10 0:30 ` [PATCH 03/20] rsync: backport libattr checking patch Armin Kuster
2016-01-10 0:30 ` [PATCH 04/20] openssh: CVE-2015-6563 CVE-2015-6564 CVE-2015-6565 Armin Kuster
2016-01-10 0:30 ` [PATCH 05/20] fontcache: allow to pass extra parameters and environment to fc-cache Armin Kuster
2016-01-10 0:30 ` [PATCH 06/20] image.bbclass: don't let do_rootfs depend on BUILDNAME Armin Kuster
2016-01-10 0:30 ` [PATCH 07/20] layer.conf: Add several allarch dependency exclusions Armin Kuster
2016-01-10 0:30 ` [PATCH 08/20] layer.conf: Add missing dependency for allarch package initramfs-framework Armin Kuster
2016-01-10 0:30 ` [PATCH 09/20] allarch: Force TARGET_*FLAGS variable values Armin Kuster
2016-01-10 0:30 ` [PATCH 10/20] texinfo: don't create dependency on INHERIT variable Armin Kuster
2016-01-10 0:30 ` [PATCH 11/20] linux-dtb.inc: drop unused DTB_NAME variable from do_install Armin Kuster
2016-01-10 0:30 ` [PATCH 12/20] glibc: use patch for CVE-2015-1781 Armin Kuster
2016-01-10 0:30 ` [PATCH 13/20] libxml2: CVE-2015-7942 Armin Kuster
2016-01-10 0:30 ` [PATCH 14/20] unzip: CVE-2015-7696, CVE-2015-7697 Armin Kuster
2016-01-10 0:30 ` [PATCH 15/20] libxml2: CVE-2015-8035 Armin Kuster
2016-01-10 0:30 ` [PATCH 16/20] openssl: CVE-2015-3194, CVE-2015-3195 Armin Kuster
2016-01-10 0:30 ` [PATCH 17/20] libxml2: CVE-2015-8241 Armin Kuster
2016-01-10 0:30 ` [PATCH 18/20] Fixes a heap buffer overflow in glibc wscanf Armin Kuster
2016-01-10 0:30 ` [PATCH 19/20] grub2: Fix CVE-2015-8370 Armin Kuster
2016-01-10 0:30 ` [PATCH 20/20] bind: CVE-2015-8000 Armin Kuster
2016-01-21 11:57 ` [PATCH 00/20] Dizzy-next pull request 2016-1 Martin Jansa
2016-01-27 11:33 ` Martin Jansa
2016-01-30 2:44 ` akuster808
2016-01-30 9:08 ` Martin Jansa
2016-01-30 12:06 ` Richard Purdie [this message]
2016-01-30 12:37 ` Martin Jansa
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=1454155589.27087.3.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.com \
--cc=martin.jansa@gmail.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