no attachments for patches. no. what part of "no" confuses you?

[Robert P. J. Day]

  *sigh* ... i had hoped that taking a break from this list even
briefly would have allowed nick krause to wander off and start a new
career as a dog walker or something but ... sadly, no. and i see he is
still, after all this time, unable to properly submit even the most
screamingly trivial patch.

  here's a fundamental rule -- do not submit patches as attachments.
don't. just don't. even plain-text attachments. no. don't. this is
explained very clearly in the file Documentation/SubmittingPatches so
that even someone as clueless as nick should be able to understand it.
and i quote:

"7) No MIME, no links, no compression, no attachments.  Just plain text.

"Linus and other kernel developers need to be able to read and comment
on the changes you are submitting.  It is important for a kernel
developer to be able to "quote" your changes, using standard e-mail
tools, so that they may comment on specific portions of your code.

"For this reason, all patches should be submitting e-mail "inline"."

  it's difficult to see how anyone can misunderstand that but ...
well, there you go. and it doesn't matter what linus might have said
on the spur of the moment once upon a time. the file
Documentation/SubmittingPatches is there for a reason -- to explain
how to, you know, submit patches. and that file, as you can see, quite
clearly says "no attachments."

  did i mention it says "no attachments"? yeah, it says "no
attachments."

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================