On Tuesday 31 March 2009 00:43:01 Bean wrote: > Hi, > > I see the main objection here is about too many new modules, and the > use of script to configure boot process.
I don't object to the latter any longer. Did you read my message? > But how about the new > parser/reader/menu_viewer model ? Nothing wrong. I have already proposed a similar idea for long: https://savannah.gnu.org/task/?7668 > If I put them back in one > normal.mod, but keep the parts separated in source, would that be > acceptable ? > > Also, some thoughts about grub2 authority. I do understand the needs > to keep source clean and safe for a boot loader, but sometimes the > process just seems too slow. For example, Colin's graphic menu patch > has been pending for almost half a year. IMO, if a patch implement a > generally useful feature, have no serious design faults, and don't > conflict with other parts of grub2, then it's safe to commit. For > small issues, we could fix it later. > > Perhaps we can add a testing branch, in which developers have more > freedom to commit their work. The maintainer can review them > periodically and merge selected parts with the main branch. Many open > source project have more than one branches, perhaps it'd work with > grub2 as well. I just feel headache when you say "open source" in our project. Please stop. About Colin's patch, I have *no idea*. I am sorry but I have a limitation. I can't do every thing suddenly. For branching, you can try. I had tried it in GRUB Legacy, but I concluded that our resources were not sufficient to have multiple lines. This might work if branches are used only for experimental purposes. Regards, Okuji _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
