<div dir="ltr">+1 for renaming ARM builds to <span style="color:rgb(33,33,33);font-family:"helvetica neue",helvetica,arial,sans-serif;font-size:13px">linux32ARMv6, </span><span style="color:rgb(33,33,33);font-family:"helvetica neue",helvetica,arial,sans-serif;font-size:13px">linux32ARMv7, </span><span style="color:rgb(33,33,33);font-family:"helvetica neue",helvetica,arial,sans-serif;font-size:13px">linux32ARMv8...</span><br><div class="GmSign">-- <br></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jun 27, 2016 at 6:48 PM tim Rowledge <<a href="mailto:tim@rowledge.org">tim@rowledge.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
> On 27-06-2016, at 9:31 AM, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com" target="_blank">eliot.miranda@gmail.com</a>> wrote:<br>
> I'd like to resolve this quickly but my favoured resolution will affect travis. I want to rename build.linux32ARM to build.linux32ARMv6 and add build.linux32ARMv7. s that ok with people?<br>
<br>
It’s a perfectly reasonable thing to do - and we’ll need ARMv8 eventually of course - but it doesn’t have a lot to do with the original problem of why Dave couldn’t build a vm on his new Pi...<br>
<br>
<br>
tim<br>
--<br>
tim Rowledge; <a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>; <a href="http://www.rowledge.org/tim" rel="noreferrer" target="_blank">http://www.rowledge.org/tim</a><br>
Strange OpCodes: NNI: Neglect Next Instruction<br>
<br>
<br>
</blockquote></div></div>