Michael <barra_cuda@xxxxxxxxxxxx> writes: > @@ -331,3 +330,21 @@ whitespaces (fatal in patches). Running 'C-u g' to > display the > message in raw form before using '|' to run the pipe can work > this problem around. > > + > +KMail > +----- > + > +This should help you to submit patches inline using KMail. > + > +1) Prepare the patch as a text file. > + > +2) Click on New Mail. > + > +3) Go under "Options" in the Composer window and be sure that > +"Word wrap" is not set. > + > +4) Use Message -> Insert file... and insert the patch. > + > +5) Back in the compose window: add whatever other text you wish to the > +message, complete the addressing and subject fields, and press send. > + This is quite interesting -- notice your own hunk header @@ ... @@ line? I do not use KMail myself, so I cannot comment on the procedure, but from the cursory look it *should* do the right thing. Only that it makes me a bit nervous to see your hunk header being line wrapped. Doubly interesting is that somebody appears to have added two message IDs. Subject: [PATCH] Documentation: add KMail in SubmittingPatches Date: Mon, 5 Feb 2007 14:27:32 +0100 User-Agent: KMail/1.9.4 Message-Id: <200702051427.32532.barra_cuda@xxxxxxxxxxxx> Message-ID: <20070205132150.123659@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html