[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151217131027.5af2a0f5.drivshin.allworx@gmail.com>
Date: Thu, 17 Dec 2015 13:10:27 -0500
From: "David Rivshin (Allworx)" <drivshin.allworx@...il.com>
To: David Miller <davem@...emloft.net>
Cc: johannes@...solutions.net, netdev@...r.kernel.org,
linux-wireless@...r.kernel.org
Subject: Re: pull-request: mac80211 2015-12-15
On Thu, 17 Dec 2015 12:04:48 -0500 (EST)
David Miller <davem@...emloft.net> wrote:
> From: Johannes Berg <johannes@...solutions.net>
> Date: Thu, 17 Dec 2015 13:44:32 +0100
>
> > On Wed, 2015-12-16 at 18:34 -0500, David Miller wrote:
> >>
> >> Something about your text encoding kept this from ending up
> >> in patchwork for some reason.
> >>
> >
> > Hm. I don't see anything special with this, seems to just be plain
> > text 8bit transfer encoding.
> >
> > Do you want me to watch out for things getting into patchwork in the
> > future?
>
> Look in the quoted text of mine, see that underline thing after
> the ">>"? Where are those coming from? Those were all over the
> place in your pull request and tripped up patchwork's parser I
> guess.
I was curious and took a look. I suspect what you're seeing are the UTF-8
<0xC2 0xA0> sequence, which translates to codepoint 0x00A0 "no-break space"
(same as in latin1). They seem to have been used in place of regular spaces
for the purpose of indenting. The Content-Type charset in Johannes' emails
is "UTF-8", so I think that's legal. Although I have no idea how Patchwork
reacts to it.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists