mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Sam Vilain <sam@vilain.net>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	linux-kernel@vger.kernel.org,
	dev-apps-thunderbird@lists.mozilla.org
Subject: Re: Mozilla Thunderbird posting instructions wanted
Date: Mon, 20 Feb 2006 21:34:46 +0000	[thread overview]
Message-ID: <200602202134.46693.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <43FA30D1.4020701@vilain.net>

On Monday 20 February 2006 21:12, 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.

Many clients have this feature, although it does not end up being presented by 
the client as quotable text. Read: any form of attachment is suboptimal.

-- 
Cheers,
Alistair.

'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

  reply	other threads:[~2006-02-20 21:34 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 [this message]
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
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=200602202134.46693.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --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 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®