<div dir="ltr">Hi Marek, <div><br></div><div>Thanks for the info. Whats the official channel?</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 16, 2014 at 1:57 AM, Marek Grac <span dir="ltr"><<a href="mailto:mgrac@redhat.com" target="_blank">mgrac@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 04/14/2014 06:31 PM, David Smith wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Wow really? You can't take work from outside your QA group despite having confirmation of it working from a QA Professional who implemented it and is currently using all the changes in his own lab?<br>
<br>
If this is an absolute must, I'm sure I can arrange to give someone external access to one of these devices, but it won't be without *additional* significant effort on my part.<br>
<br>
Let me know what I can do to help resolve this.<br>
<br>
</blockquote></div>
For upstream it is not a problem but for RHEL accepting it will mean that we will support this for X years (X > 10) for every customer.<br>
<br>
I'm developer, so I'm not the one who decides what should be included - please use the official channel, so it will be read by right people.<span class="HOEnZb"><font color="#888888"><br>
<br>
m,<br>
</font></span></blockquote></div><br></div>