| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 10 Jul 2007 12:44:22 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: linux-kernel@...r.kernel.org Subject: avoiding rejects 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists