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: Sat, 26 Apr 2008 13:27:17 +0200 From: Sam Ravnborg <sam@...nborg.org> To: Adrian Bunk <bunk@...nel.org> Cc: Harvey Harrison <harvey.harrison@...il.com>, Mauro Carvalho Chehab <mchehab@...radead.org>, Linus Torvalds <torvalds@...ux-foundation.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: If you want me to quit I will quit Hi Adrian. > Why do other people get over 100 checkpatch fixes into the tree at once > or Linus applies patches directly bypassing the maintainers (like the > one you sent just before [3], which I've also already sent before [4]) > but my patches bitrot forever? The patches you submit touches all parts of the kernel tree. And you do a good job in finding the relevant receivers. To me you are partly in the saem situation as Andrew in that you handle a great deal of patches touching a lot of different subsystems. We all know that the patch acceptance ratio differ a lot between the different maintainers and the way Andrew deals with this seems quite effective. After enough tries Andrew just submit the pacthes himself direct to Linus. But almost never without trying to get the relevant Maintainer to take it first. So in your position I would keep all patches in a place so they can be sucked into -next and regular spam the relevant amintainers with their patches. When the merge window opens then submit the rest to Linus with a noe that they have been sent to Maintainers without any feedback previously. This is not far away from what you do now and should not create that big frustrations (I hope). Sam -- 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