<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 9 January 2016 at 03:27, Andre McCurdy <span dir="ltr"><<a href="mailto:armccurdy@gmail.com" target="_blank">armccurdy@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 id=":2vg" class="a3s" style="overflow:hidden">For patches which fix 'correctness' issues uncovered by musl maybe<br>
it's better to apply the patches unconditionally, so they get some<br>
test cover from non-musl builds?<br>
<br>
Especially true in this case - see below.</div></blockquote></div><br>Agreed. Patches should only be applied on overrides if they negatively impact other configurations, so a strict correctness patch should always be applied whereas a patch that stubs out glibc-specific code would be applied on specific configurations.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>