<br><br><div class="gmail_quote">On Thu, Sep 2, 2010 at 12:18 PM, Adam Williamson <span dir="ltr"><<a href="mailto:awilliam@redhat.com">awilliam@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Thu, 2010-09-02 at 12:12 +1000, Rodd Clarkson wrote:<br>
<br>
</div>To be frank, they don't have time to look at everything, and suspend is<br>
a bit of a way down the list. They are aware of your bug - I know<br>
because one of the kernel team asked me if I was aware of any problems<br>
with 2.6.34 more serious than suspend issues, so obviously they've seen<br>
yours, but haven't had time to respond to it yet.<br>
<div><div></div><br></div></blockquote><div>To be frank, I don't have time to test things at the request of developers if my test results are just going to be ignored.<br><br>It's a lot of work to test stuff (as you would know) and no-one likes to be ignored. Even a simple not in the bug report saying that there was a compelling reason for upgrading the kernel to 2.6.34 that meant that the issue wouldn't be resolved and that I should make sure that I avoid updates if I require suspend/resume to work can't be too much pressure on a developer time - this of course assumes that there was a compelling reason and that it wasn't upgrades for the sake of upgrades in a stable product.)<br>
<br>Might I ask what great good has come from this?<br><br><br>Rodd<br></div></div>