Re: Best way to send several patches

[Roland Dreier]

 > 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@xxxxxxxxx> || 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/