From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: David Miller <davem@davemloft.net>
Cc: <joe@perches.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH V3] wanrouter: Remove it and the drivers that depend on it
Date: Wed, 14 Nov 2012 10:23:39 -0500 [thread overview]
Message-ID: <20121114152339.GA22933@windriver.com> (raw)
In-Reply-To: <20121114060759.GA17128@windriver.com>
[Re: [PATCH V3] wanrouter: Remove it and the drivers that depend on it] On 14/11/2012 (Wed 01:07) Paul Gortmaker wrote:
> [Re: [PATCH V3] wanrouter: Remove it and the drivers that depend on it] On 13/11/2012 (Tue 20:44) David Miller wrote:
>
> >
> > Paul, you can't have HTML content to the list and one of your MIME
> > sections was HTML, so it was rejected by vger's filters.
> >
> > 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. It looks like it arrived that way to the
list archivers too, and they failed to do anything sensible with their
copy of your message as well.
http://marc.info/?l=linux-netdev&m=135284894104364&w=2
Paul.
next prev parent reply other threads:[~2012-11-14 15:23 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 [this message]
2013-01-11 0:28 ` Jan Engelhardt
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=20121114152339.GA22933@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).