All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Helsley <matthltc@us.ibm.com>
To: Sam Vilain <sam@vilain.net>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	dev-apps-thunderbird@lists.mozilla.org
Subject: Posting Patches with Evolution (WAS Re: Mozilla Thunderbird posting instructions wanted)
Date: Mon, 20 Feb 2006 14:11:15 -0800	[thread overview]
Message-ID: <1140473475.7357.379.camel@stark> (raw)
In-Reply-To: <43FA30D1.4020701@vilain.net>

On Tue, 2006-02-21 at 10:12 +1300, Sam Vilain wrote:
> Alexey Dobriyan 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.
> > 
> > I'll put instructions somewhere on -kj website and point every
> > unsuspecting new guy to them.
> 
> Evolution has an option for setting the Content-Disposition: inline 
> header on individual attachments; I haven't seen the same option in 
> thunderbird.
> 
> Sam.

	Even better, you can inline plain text in Evolution if you switch the
text style to "Preformat" just before going to the "Insert" menu,
selecting "Text file...", and selecting a file to insert. This works
even with HTML-formatted output turned off in your preferences.

Cheers,
	-Matt Helsley


  parent reply	other threads:[~2006-02-20 22:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 21:03 Mozilla Thunderbird posting instructions wanted 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   ` Matt Helsley [this message]
2006-02-20 21:12 ` 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
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=1140473475.7357.379.camel@stark \
    --to=matthltc@us.ibm.com \
    --cc=adobriyan@gmail.com \
    --cc=dev-apps-thunderbird@lists.mozilla.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@vilain.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.