| 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: Thu, 05 Aug 2010 15:02:05 -0700 From: Roland Dreier <rdreier@...co.com> To: Bjarke Istrup Pedersen <gurligebis@...too.org> Cc: linux-kernel@...r.kernel.org Subject: Re: Best way to send several patches > The question is, should I just send them all to this mailinglist > (Section 3 of Documentation/SubmittingPatches - the one with the patch > bomb - suggest that this is a bad idea), or how should I do it? (I > have only submitted a single patch before, so I didn't have to worry > about that back then). I would suggest sending a small batch of patches (say, four or five at most) and see how that goes. That way, in case you make some mistake in formatting or something, you don't have to send another huge pile when you resend. Once your initial batch is accepted and you have the hang of submitting patches, then you can submit bigger batches. But I would recommend having each batch have a common theme. For example there was the recent series of 42 fixes for confusing if indentation -- a big batch of fixes for the same problem in different places, which is exactly the right way to do things. - Roland -- Roland Dreier <rolandd@...co.com> || For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/index.html -- 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