When I sent the original rfc message to the mailing list, it was denied for being over 60k, hence my question. Looking at the raw email, I suspect that gmail is inflating the size dramatically by sending both plaintext and html versions.
The document, SubmittingPatches, also refers to the large patch issue. On re-reading it, I see it puts the limit at 300k, which this is nowhere near. I'll see about using git send-email for the next attempt at sending it in. On Oct 24, 2014 11:19 AM, "Mark Brown" broonie@kernel.org wrote:
On Fri, Oct 24, 2014 at 09:48:37AM -0500, Jonathan Bennett wrote:
Oh, also, this patch is a bit big for the mailing list, what is the preferred method for sending in large patches to look at? I can attach, throw it on github, put it on an http server, etc.
You need to follow the procedure in SubmittingPatches, that means you need to post your code to the list.