From: Jan Engelhardt <jengelh@inai.de>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: David Miller <davem@davemloft.net>,
joe@perches.com, netdev@vger.kernel.org
Subject: Re: [PATCH V3] wanrouter: Remove it and the drivers that depend on it
Date: Fri, 11 Jan 2013 01:28:04 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.01.1301110118390.3948@nerf07.vanv.qr> (raw)
In-Reply-To: <20121114152339.GA22933@windriver.com>
On Wednesday 2012-11-14 16:23, Paul Gortmaker wrote:
>> >
>> > Please repost with the HTML stuff removed.
>>
>> Ah crap. I'd replied via gmail ; today and occasionally in the past as
>> a convenient short cut when not reading netdev with a "normal" MUA. And
>> this is not the 1st time gmail has randomly decided to be "helpful" by
>> mangling plain text like this. Well, I'll be having no more of that BS.
>
>I was curious to better figure out what triggered this, now that it
>isn't 1AM. It seems the original wasn't plain text, and that gmail
>didn't know what else to do with the content from your message when it
>arrived as base64 encoded.
>http://marc.info/?l=linux-netdev&m=135284894104364&w=2
I only wonder which component is at fault here, the producer side (it
gives the following headers),
Content-Type: Text/Plain; charset=iso-8859-7
Content-Transfer-Encoding: base64
(and the _absence_ of any MIME chunkwrapping)
or the receiver side. (Al)Pine and derivates displays the message
fine, marc.info does not, and gmail presents the body after literally
taking a stab at it.
prev parent reply other threads:[~2013-01-11 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 22:36 [PATCH V3] wanrouter: Remove it and the drivers that depend on it Joe Perches
2012-11-13 23:22 ` David Miller
[not found] ` <CAP=VYLqiLpVn99bp08gkSQ+jLFiw8T7vsohJ6e+TdzOtyDwKBQ@mail.gmail.com>
2012-11-14 1:44 ` David Miller
2012-11-14 6:08 ` Paul Gortmaker
2012-11-14 15:23 ` Paul Gortmaker
2013-01-11 0:28 ` Jan Engelhardt [this message]
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=alpine.LNX.2.01.1301110118390.3948@nerf07.vanv.qr \
--to=jengelh@inai.de \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.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 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.