public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Mozilla Thunderbird posting instructions wanted
Date: Mon, 20 Feb 2006 22:25:51 +0100	[thread overview]
Message-ID: <43FA33DF.1050200@keyaccess.nl> (raw)
In-Reply-To: <20060220210349.GA29791@mipter.zuzino.mipt.ru>

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

Oh, give it up...

 > Sending plain text attachments is OK with me, but, heh, people do post
 > patches inline and screw themselves.

Personally I'd simply advocate plain text attachments. One thing though; 
if you are going to, please make note of the long (long) standing bug in 
TB that has it send all attachments (including plaintext ones) Base64 
encoded when the outgoing encoding is set to UTF-8.

I do normally have outgoing set to UTF-8 and for example forgot to 
disable that earlier today when I sent an OOPS as an attachment. You 
don't immediately notice this yourself, since TB simply decodes it again 
when viewing...

Rene.

  parent reply	other threads:[~2006-02-20 21:25 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   ` 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 [this message]
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=43FA33DF.1050200@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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