<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WORKSFORME - Incorrect image stretching with Render in RepeatPad mode, NV50" href="https://bugs.freedesktop.org/show_bug.cgi?id=32855#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WORKSFORME - Incorrect image stretching with Render in RepeatPad mode, NV50" href="https://bugs.freedesktop.org/show_bug.cgi?id=32855">bug 32855</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to <a href="show_bug.cgi?id=32855#c9">comment #9</a>) > It is user-hostile and unprofessional to mass-close bugs, even very old > bugs, without making any attempt to reproduce the problem first. > <a href="http://www.jwz.org/doc/cadt.html">http://www.jwz.org/doc/cadt.html</a> I wasn't a big fan of it either (despite proposing it and doing it). But look at it from the project's standpoint -- volunteer based (and not exactly a big team), high code churn rate (esp 1-2 years ago), high hardware death(/replacement) rate, large variety of hardware, 400+ bugs deep, of which 200 are from more than 2 years without an update. So I didn't see a better way of getting a handle on the situation. Of the 200+ bugs I closed, about 10 have gotten follow-up comments of any sort (either that it's been fixed/hardware gone/still a problem). I'm individually pinging newer bugs, and I'm not having a great response rate either (but better). Besides, you always have the option of re-opening the same bug and providing updated information. As a bug filer, I think it's reasonable to expect you to be the main tester (at least with nouveau).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>