> > Whether or not an update occurs, I would suggest that patches have a > > place on the grub ftp site, as the official releases will always fall > > behind the newest hardware. An "unsupported patches" directory, with a > > use-at-your-own-risk policy, would be a useful source for adminstrators > > looking to use grub with their newest toys, and would encourage the > > submission of code and ideas which may be useful to the grub maintainers. > > I agree, and the BTS exists for the very purpose. Isn't the BTS enough?
Almost, I suspect. I just took a look at the grub website (http://www.gnu.org/software/grub/) for the first time in a few months. I spent a few minutes trying to navigate my way to a browsable list of submitted-but-unmerged patches. I couldn't find one. I suspect someone more familiar with the website would have found it, so I guess I'm just suggesting that you/someone make it easier to find. It's probably just a simple matter of putting a button/link on the main page (probably in the download section) that submits the appropriate query to the BTS when clicked. P.S. A mail client I've tinkered with in the past has a webpage listing unsupported patches. It's maintained by someone who isn't one of the core maintainers for the program. It's at http://www.thewildbeast.co.uk/sylpheed/ Anyone (with a web account) could step up and volunteer to maintain such a page for grub. _______________________________________________ Bug-grub mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-grub
