<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 2 December 2014 at 13:05, Chris Murphy <span dir="ltr"><<a href="mailto:lists@colorremedies.com" target="_blank">lists@colorremedies.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, Dec 1, 2014 at 6:17 PM, Stephen John Smoogen <<a href="mailto:smooge@gmail.com">smooge@gmail.com</a>> wrote:<br>
<br>
> 1) A problem is identified.<br>
> 2) Profile the problem and show where it might be happening.<br>
> 3) Some amount on fixing the problem is done.<br>
> 4) Find that the problem isn't there and there is no quick fix.<br>
> 5) Throw away that solution and implement another one.<br>
> 6) Deal with flame wars about any and all changes during this from people<br>
> the problem doesn't occur to.<br>
><br>
> Projects which use words like "we" before 3 or 4 usually never get to 3 or 4<br>
> due to the amount of "why is your problem now my work?" response from<br>
> everyone from developers to random people on the lists.<br>
><br>
> Currently you are at 1, and you have tried to jump to 3 with the Arch<br>
> solution. You need to profile the Arch solution to see if it really works or<br>
> if it only works if you run an X11/twm and nothing fancier than Mosaic from<br>
> 1997. [Or without X11 at all.. that is the usual way to get a large power<br>
> improvement on a laptop.]<br>
<br>
</span>Question: Shouldn't the evaluation and fix be targeted at Rawhide<br>
first, and then see about "backporting" demonstrated fixes to Fedora<br></blockquote><div><br></div><div>It should always be in rawhide. I doubt that it would be ready anytime near Fedora 22 or 23.</div><div> </div></div>-- <br><div class="gmail_signature"><div dir="ltr">Stephen J Smoogen.<br><br></div></div>
</div></div>