<div dir="ltr">On 19 September 2017 at 00:16, Trevor Woerner <span dir="ltr"><<a href="mailto:twoerner@gmail.com" target="_blank">twoerner@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It doesn't make sense to carry these large patches against pseudo in<br>
OE itself. Isn't pseudo one of the tools under The Yocto Project<br>
umbrella? Adding patches to a recipe is what happens when upstream<br>
isn't under our control, isn't responsive, or isn't cooperating.<br>
<br>
Can someone volunteer to be the active maintainer of it and get commit<br>
access? I'll volunteer, if nobody else does. But if I become the<br>
maintainer, I'll need some time to get up-to-speed, or some potential<br>
support from the current maintainer.</blockquote><div><br></div><div>This patch may not yet be acceptable "upstream" but is sufficient for our purposes, and we've obviously got a good relationship with "upstream" so carrying it in oe-core is a short-term measure.</div><div><br></div><div>Ross</div></div></div></div>