<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Unknown Card-Ids (3371|1019|2125), Chipset: P4M900/VN896/CN896" href="https://bugs.freedesktop.org/show_bug.cgi?id=94130#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Unknown Card-Ids (3371|1019|2125), Chipset: P4M900/VN896/CN896" href="https://bugs.freedesktop.org/show_bug.cgi?id=94130">bug 94130</a> from <a class="email" href="mailto:noloader@gmail.com" title="Jeffrey Walton <noloader@gmail.com>"> Jeffrey Walton</a> <pre>> Well, we are using git, which means that the past is fully present in the > present. :) You could make a checkout of just before you started the big > overhaul, that is before removing the known-device table. Call that the > 0.3.4 > branch, and make a release from there. And then maybe even a few follow-up > releases, until you feel the 0.4.0 master branch is in a releasable state. > > git checkout b4624fdb > git checkout -b release_0_3_4 > > And when you're done there rolling a release, you do: > > git checkout master > > and continue toward 0.4.0. > > You see, getting a release out is not just about getting as many bugs fixed > as > possible. It is also a signal to downstream that there is some activity. > It > will attract bug reports, and maybe even help. And even if 0.3.4 would fix > just one or two little bugs, some people will be helped by it. So... it's > worth it getting it out there. +1 here. Nearly every ISO I have tried is broken due to the Xserver crash for the VIA P4M900. That includes Debian, Ubuntu, Lubuntu and Fedora. To get just one or two bugs fixed so they can build a new ISO means the install can occur/continue. That's a huge win for users of these thin clients.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>