3 ms·
The problem would be easily solved by: 1)Requiring the patch be posted online somewhere, not in the email message as an attachment. Criteria could be set, such
by KennyBlanken 3y ago
The problem would be easily solved by:
1)Requiring the patch be posted online somewhere, not in the email message as an attachment. Criteria could be set, such as "must be via https, and something that will handle the volume of hits without becoming unreachable due to insufficient quota, server resources, or quota." Or set up a patch hosting server. Etc.
2)Dividing the kernel into major categories like every other major open source software project, and having patch lists for those categories. The main list should only be for announcements and discussions that require a broad audience.
- CuriousCosmic 3y ago> 2)Dividing the kernel into major categories like every other major open source software project, and having patch lists for those categories. The main list should only be for announcements and discussions that require a broad audience. Uhhhh the linux kernel mailing list is made up of at least a hundred separate mailing lists with development happening on the more specific mailing lists and a focus on maintaining/integration occurring on the more general lists.
- seba_dos1 3y agoDid you expect a HN commenter to actually research the thing they're commenting on? :P