<div dir="ltr">I'm sorry, for some reason this thread in Gmail starts with the morty review you've sent, but when I look in my favorite mutt, I see that my replies were linked with pyro review where you're right the files aren't included.<div><br></div><div>Still I would like to see what's the diff between gcc-6.4 in morty and pyro and gcc-6.4 which was in master (and there is still gcc-6.3 in rocko which should imho be upgraded first to preserve continuity).</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Mar 4, 2018 at 2:35 PM, Martin Jansa <span dir="ltr"><<a href="mailto:martin.jansa@gmail.com" target="_blank">martin.jansa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Are we both talking about the same morty-next?</div><div><br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">docker-shr @ ~/openembedded-core $<span> </span></span>git log origin/morty-next -- meta/recipes-devtools/gcc/gcc-<wbr>6.4/CVE-2016-4490.patch</div><span class=""><div>commit a926f3986174b67375c4486e5b3f27<wbr>ad3b939e28</div><div>Author: Juro Bystricky <<a href="mailto:juro.bystricky@intel.com" target="_blank">juro.bystricky@intel.com</a>></div><div>Date: Thu Mar 1 13:38:08 2018 -0800</div><div><br></div><div> gcc6: Upgrade to 6.4.0 (latest stable series release)</div><div> </div></span><div> Changed BINV and PV from 6.2.0 to 6.4.0</div><span class=""><div> Modified BASEURI to load xz tarball instead of bz2</div><div> </div><div> Backported series of patches from <a href="https://github.com/hjl-tools/gcc.git" target="_blank">https://github.com/hjl-tools/<wbr>gcc.git</a></div><div> branch /hjl/indirect/gcc-6-branch/<wbr>master which contains</div><div> an IA patch series for security related issues</div><div> </div><div> ubsan-fix-check-empty-string.<wbr>patch : removed, already applied</div><div> </div></span><div> Signed-off-by: Juro Bystricky <<a href="mailto:juro.bystricky@intel.com" target="_blank">juro.bystricky@intel.com</a>></div><div>docker-shr @ ~/openembedded-core $ git show -1 a926f3986174b67375c4486e5b3f27<wbr>ad3b939e28 -M | grep CVE-2016-4490.patch</div><div>diff --git a/meta/recipes-devtools/gcc/<wbr>gcc-6.2/CVE-2016-4490.patch b/meta/recipes-devtools/gcc/<wbr>gcc-6.4/CVE-2016-4490.patch</div><div>rename from meta/recipes-devtools/gcc/gcc-<wbr>6.2/CVE-2016-4490.patch</div><div>rename to meta/recipes-devtools/gcc/gcc-<wbr>6.4/CVE-2016-4490.patch</div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Mar 4, 2018 at 2:26 PM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@<wbr>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>On Sun, 2018-03-04 at 13:08 +0100, Martin Jansa wrote:<br>
> And the same with<br>
> meta/recipes-devtools/gcc/gcc-<wbr>6.4/CVE-2016-4490.patch<br>
> which isn't included in SRC_URI since:<br>
<br>
</span>As far as I can tell this isn't included in the patch or the<br>
repository?<br>
<br>
Cheers,<br>
<br>
Richard<br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>