On Tue, 10 Jul 2007, Andrew Morton wrote: > There are many situations where patching the kernel involves adding a new > item to a list, such as: > > - adding a makefile line > - adding a new #include > - adding a new Kconfig entry > - adding a new PCI ID > - adding a record to feature-removal.txt > - adding a new sysctl table entry > - etc > > Of course, everyone just sticks the new entry at the end of the existing > entries. This strategy carefully maximises the opportunity for patch > rejects and leads to unhappiness. > > Most of these lists are unordered anyway, so inserting the new item at a > randomly-chosen position is a better approach than just appending it.
Really? #includes should be sorted alphabetically Lots of other stuff should be sorted numerically/alphabetically Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/