public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: jim owens <jowens@hp.com>, Randy Dunlap <rdunlap@xenotime.net>,
	linux-doc@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Dan Carpenter <error27@gmail.com>,
	Jes Sorensen <jes.sorensen@gmail.com>
Subject: Re: [PATCH] Documentation/email-clients.txt: clarify Thunderbird section
Date: Thu, 10 Dec 2009 16:05:47 -0600	[thread overview]
Message-ID: <4B2170BB.2070001@nortel.com> (raw)
In-Reply-To: <4B2120F2.3090301@tuffmail.co.uk>

On 12/10/2009 10:25 AM, Alan Jenkins wrote:

> The RFC for format=flowed says that it should escape lines which start 
> with a space (by "space stuffing" - prepending an additional space).  So 
> in theory it should completely break patches.   And indeed it does 
> <http://gcc.gnu.org/ml/java-patches/2003-q2/msg00315.html>
> 
> Using HTML preformat in current versions of Thunderbird appears to send 
> with a format=flowed content-type, and then violates the RFC by not 
> performing any space-stuffing.
> 
> So if I look at format=flowed patch in my Sent email folder, I see that 
> the message viewer correctly strips the first leading space in each 
> line.  I.e. it breaks if you use copy+paste to get the patch out of 
> Thunderbird (or any other format=flowed aware client).  File->Save As 
> preserves the spaces though, allowing the patch to be applied.

Hmm...I'm using Thunderbird 3 beta4, and it appears that when sending
via the "preformat" mechanism it actually does perform space-stuffing.
This is visible as an extra leading space when looking at the raw source
of the sent (or received) email via ctrl-U.

However, if one turns off format=flowed, but leaves wrap set to 72, then
the html preformat works without having to set the wrap to 0.

Thanks,

Chris

  parent reply	other threads:[~2009-12-10 22:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 14:57 [PATCH] Documentation/email-clients.txt: clarify Thunderbird section Alan Jenkins
2009-12-10 15:16 ` jim owens
2009-12-10 16:25   ` Alan Jenkins
2009-12-10 16:47     ` jim owens
2009-12-10 22:05     ` Chris Friesen [this message]
2009-12-10 22:16       ` Randy Dunlap

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=4B2170BB.2070001@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=error27@gmail.com \
    --cc=jes.sorensen@gmail.com \
    --cc=jowens@hp.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.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