[OE-core] [PATCH 00/20] Dizzy-next pull request 2016-1
Richard Purdie
richard.purdie at linuxfoundation.org
Sat Jan 30 12:06:29 UTC 2016
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
More information about the Openembedded-core
mailing list