<div dir="ltr"><div>> <span style="font-size:12.8px">I have merged this to dizzy though.<br></span><br></div><div>Thanks!</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 30, 2016 at 1:06 PM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sat, 2016-01-30 at 10:08 +0100, Martin Jansa wrote:<br>
> > that was a patch from the patch queue and affect glibc below 2.21<br>
> so<br>
><br>
> glibc/wscanf: CVE-2015-1472<br>
><br>
> looks like better subject<br>
><br>
> > Dizzy 1.7.4 is not planned yet.<br>
><br>
> I don't care about point releases, I care only about contents of<br>
> release branch, can it be merged to dizzy branch?<br>
<br>
</span>I was hoping the branch would get corrected so I could then just pull<br>
the correct commits. I suspect Armin didn't realise I was waiting for<br>
that.<br>
<br>
In the interests of expedience, I've reworded that commit and merged<br>
the branch.<br>
<br>
There are a couple of tweaks that would make things easier for me to<br>
take these:<br>
<br>
a) Could you in the 00/XX series header in future confirm you've<br>
checked and that these issues are addressed in the later stable<br>
branches? I do worry that for example there may be unaddressed issues<br>
in fido.<br>
<br>
b) If you could share an oe-core contrib branch with these in, it does<br>
make it easier for me to merge them. I can deal with that comparatively<br>
easily though.<br>
<br>
I have merged this to dizzy though.<br>
<br>
Cheers,<br>
<br>
Richard<br>
<br>
<br>
<br>
</blockquote></div><br></div>