From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: "Nish Aravamudan" <nish.aravamudan@gmail.com>
Cc: adobriyan@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Mozilla Thunderbird posting instructions wanted
Date: Mon, 20 Feb 2006 14:20:35 -0800 [thread overview]
Message-ID: <20060220142035.6ccbe6d9.rdunlap@xenotime.net> (raw)
In-Reply-To: <29495f1d0602201330i78d5538bwe4c771593f09ea97@mail.gmail.com>
On Mon, 20 Feb 2006 13:30:59 -0800 Nish Aravamudan wrote:
> On 2/20/06, Alexey Dobriyan <adobriyan@gmail.com> wrote:
> > This POS is pretty popular among kernel janitors, so, can someone who
> > is successfully using it, please, post crystally clear step-by-step
> > instructions on how to send a foo.patch:
> > inline
> > with tabs preserved
> > with long lines preserved
> >
> > Sending plain text attachments is OK with me, but, heh, people do post
> > patches inline and screw themselves.
>
> Randy D. eventually agreed that there was a way, IIRC:
>
> http://lkml.org/lkml/2005/12/27/191
>
> Probably can work your way through the thread to figure out how (I use mutt :)
Yep, the odd part is not to disable html email.
Then when composing a message, there is a drop-down box for a format
selection. While the cursor is in the body area, change the format
from default "Body text" to Preformat, and then copy-n-paste the patch.
At least that's what worked for me.
---
~Randy
next prev parent reply other threads:[~2006-02-20 22:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 21:03 Alexey Dobriyan
2006-02-20 21:12 ` Sam Vilain
2006-02-20 21:34 ` Alistair John Strachan
2006-02-20 23:11 ` Alan Cox
2006-02-20 22:11 ` Posting Patches with Evolution (WAS Re: Mozilla Thunderbird posting instructions wanted) Matt Helsley
2006-02-20 21:12 ` Mozilla Thunderbird posting instructions wanted Jesper Juhl
2006-02-20 21:25 ` Rene Herman
2006-02-20 22:22 ` Jeff Garzik
2006-02-20 21:30 ` Nish Aravamudan
2006-02-20 22:20 ` Randy.Dunlap [this message]
2006-02-20 22:31 ` Phillip Susi
2006-02-20 23:46 ` Frank Sorenson
2006-02-21 0:07 ` Antonino A. Daplas
2006-02-22 1:12 ` Martin Bligh
2006-02-22 1:49 ` Ray Lee
2006-02-22 1:57 ` Martin Bligh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060220142035.6ccbe6d9.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®